Does your config contain the ServerName directive?
If it contains
then Apache might interpreted it as using the default port:
If so, try changing that directive to:
P.S. HTTP_HOST is not completely reliable. It contains whatever header was
sent by the user, so it can be spoofed.
On 5/22/2012 1:39 PM, Bradley Stone wrote:
SCRIPT_URI is blank (I don't show that as available) and HTTP_HOST
I have searched and found others running Apache with this issue, but
it was some time ago. So I wonder if it's a bug that somehow
transferred over when IBM used Apache as a base for their HTTP server.
I still miss the CERN server. :)
I find it hard to believe that this has went without getting caught
for this long... I will keep looking.. thanks!
On Tue, May 22, 2012 at 11:26 AM, Alan Seiden <alan@xxxxxxxxxxxxxx> wrote:
For me, SERVER_PORT shows the correct port on 7.1.
What do SCRIPT_URI and HTTP_HOST contain?
Alan Seiden, PHP for IBM i Consultant and Advocate
PHP Lead Developer, new toolkit for IBM i
Zend Framework certified contributor
On 5/22/2012 12:16 PM, Bradley Stone wrote:
I was putting together an application for a client and planned on
using the SERVER_PORT as part of the program to know if the requests
were internal or external (ie port 80 is external, outside the LAN
coming through the firewall) and something like port 81 is inside the
So, created on instance that points to conf running port 80, and
another instance that points to conf running port 81.
Well, SERVER_PORT always returns port 80, no matter which server
instance I'm connecting to.
This is V5R4. I verified the same thing happens on my machine which
is also V5R4.
Any ideas? Thanks!
As an Amazon Associate we earn from qualifying purchases.