Synopsis: wrong SCRIPT_URI when portnumber != 80 State-Changed-From-To: open-analyzed State-Changed-By: marc State-Changed-When: Fri Sep 26 07:47:51 PDT 1997 State-Changed-Why: If it is something that only appears in PHP, we really can't support it.
What happens if you call a CGI-script like printenv? Does it have the correct SCRIPT_URI? If so, this really looks like a problem in PHP.
