https://issues.apache.org/bugzilla/show_bug.cgi?id=47986
Summary: ProxyBadHeader documentation unclear about context
Product: Apache httpd-2
Version: 2.2-HEAD
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Documentation
AssignedTo: [email protected]
ReportedBy: [email protected]
Ref: http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxybadheader
The ProxyBadHeader is unclear about which response status header lines it is
referring. Although it can be inferred that a 'response' belongs to the
backend/remote server it could be confused with the client request ones.
I'm unsure about the wording: the introduction on proxy states that for a
forward proxy the remote is a /origin server/, while for a reverse proxy that
would be a /back-end server/. Maybe 'remote server' is a fit for both cases.
Then maybe the short description "Determines how to handle bad header lines in
a response" could be rephrased as "Determines how to handle bad header lines in
a response from a remote server". Which helps immediatly realize that this
option refers to the client part of the proxy.
Similarly the long description could explictly say "[...] if it receives
syntactically invalid header lines (i.e. containing no colon) from a remote
origin (forward proxy) or back-end (reverse proxy) server." (maybe akward I
guess)
And by the way, looking at httpd-2.2.x/modules/proxy show that ProxyBadHeader
is internally stored as proxy_server_conf.badopt althouth it is only used in
http_proxy.c. Since this option looks HTTP-specific (and not a fit for AJP or
FTP), shouln't it be moved to the http_proxy doc ?
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
