Port restriction

It’s not a restirction per sey. WordPress is designed to run inside a web server, not on a specific port. You can configure the web server to listen to any port, but you can’t tell it ‘Run this on port 80 and this on port 8080’

Multisite tells me I can’t have a multisite setup if I’m not running on 80 or 443.

I’m wondering what technical problem multisite is working around by only letting users run their installs on ports 80 or 443.

Seems odd, but I’m sure there’s a reason.

If you want to run on an off port, frontend your install with Nginx, squid or varnish.

Ron, what is the reason for this? Why should WordPress care what port it’s on?

Hrm, I think what we have here is a failure to communicate.

Let’s say I wanted to change the code for WordPress Multisite to no longer require using a privileged port. Maybe because I’m running behind a reverse proxy, maybe because I don’t have root access, maybe because I’m just stubborn.

So whatever the reason I want to change it, let’s take it as a given that I want to change it.

I’m wondering if anyone knows why the restriction is there in the first place. When I start trying to change the code, I’d rather go in knowing the really hard, crazy problem that running on only 80 or 443 solves.

Thanks in advance.