protocol/7079: Server sends reference to RFC2068 in error 400 entity, should be RFC2616

[Alexey Toptygin <al...@wam.umd.edu>]

>Number:         7079
>Category:       protocol
>Synopsis:       Server sends reference to RFC2068 in error 400 entity, should be RFC2616
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Jan 17 01:00:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     alexeyt@wam.umd.edu
>Release:        1.3.12
>Organization:
apache
>Environment:
Apache/1.3.12 (Unix)  (Red Hat/Linux) PHP/3.0.15 mod_perl/1.21
Linux css-b-322 2.2.18 #2 Sat Jan 6 09:35:46 EST 2001 i686 unknown
egcs-2.91.66
>Description:
For a request containing no "Host:" header field, the server responds:

client sent HTTP/1.1 request without hostname (see RFC2068 section 9, and 14.23)

this should read RFC2616, as RFC2616 obsoletes RFC2068, and Apache 1.3 
claims to be RFC2616 compliant.
>How-To-Repeat:
$ telnet www.apache.org 80
GET / HTTP/1.1

>Fix:
change the string.
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database 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!     ]