www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Pimlott <piml...@mat.harvard.edu>
Subject documentation/4326: UseCanonicalName disdocumented
Date Thu, 29 Apr 1999 04:37:09 GMT

>Number:         4326
>Category:       documentation
>Synopsis:       UseCanonicalName disdocumented
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          doc-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Apr 28 21:40:01 PDT 1999
>Originator:     pimlott@mat.harvard.edu
>Release:        1.3.3
The documentation for UseCanonicalName states that when it is enabled,
"The CGI variables SERVER_NAME and SERVER_PORT will be constructed from
the client supplied values as well. "  This is not true--SERVER_PORT
disregards the client-supplied host as noted in http_core.c.

That said, another directive controlling whether to use the supplied
port would be very helpful.  Sometimes, I need to access apache through
a TCP tunnel (the userspace kind) and need to know what port the client is using.
Clean up all the mentions of port in the UseCanonicalName directive
documentation and emphasize that the port is the one on which the
connection arrived.
Add a new directive to toggle which port is reported.
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]

View raw message