You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/01/15 21:35:49 UTC

DO NOT REPLY [Bug 16137] New: - Max-Forwards MUST NOT be added

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16137>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16137

Max-Forwards MUST NOT be added

           Summary: Max-Forwards MUST NOT be added
           Product: Apache httpd-2.0
           Version: HEAD
          Platform: All
               URL: http://coad.measurement-factory.com/cgi-
                    bin/coad/GraseInfoCgi?info_id=test_clause/rfc2616/doNotA
                    ddHdr-Max-Forwards
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: mod_proxy
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: coad@measurement-factory.com


Looks like a possible RFC 2616 MUST violation.  HTTP
specifically does not allow intermediaries to add
Max-Forwards header (see bug report URL or links from 
the test case trace for RFC quotes). 

A different way to detect loops should be used 
(Via: or an extension header).

See attached trace(s) for details and ways to reproduce
the violation mentioned above.

Test case IDs in the trace link to human-oriented test case
description and RFC quotes, if available.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org