The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Using the HTTPS port or something else for port 80

My method of developing websites involves separating static and dynamic content to be delivered from different daemon servers ... its a performance enhancement - plus you can always optimize each daemon for the content that it will provide (ex. set keepAlive to off for WWW and keep it on for static).

So PHP gets loaded from WWW (or the domain alone) and anything static comes from static.website.com.

It works, but when I'm loading static content with AJAX then the browser (pretty much any browser) will trigger a security error because it sees it as a different domain. This also is an issue for CSS behaviours (htc files) and dynamic scripts (creating <script> tags).

Well, I guess one solution is to use the same domain, but change the port to something else other than port 80.

website.com:8080/static_content/file.css

This also works, but I'm just wondering if anything other than port 80 will be accepted? You never know if a particular school or institution will block anything else for HTTP other than port 80.

Is this true, or can I comfortably use port 8080?

Also, what about if I use the HTTPS port (port 443)? What happens if the daemon listening on that port doesn't have SSL enabled?