You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Petter M�hl�n <pe...@chello.se> on 2000/10/13 11:42:01 UTC
general/6666: Reason-phrase omitted from 200 response, which is a deviation from the HTTP/1.1 spec
>Number: 6666
>Category: general
>Synopsis: Reason-phrase omitted from 200 response, which is a deviation from the HTTP/1.1 spec
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Fri Oct 13 02:50:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator: petter.mahlen@chello.se
>Release: 1.3.12
>Organization:
apache
>Environment:
The search.apache.org server, actually, as of today (13th of October)
>Description:
An HTTP/1.1 POST to the search.apache.org resulted in a 200 response as follows:
"HTTP/1.1 200" <CRLF>
The problem is that according to the spec (rfc 2616, section 6.1):
status-line = http-version SP status-code SP reason-phrase CRLF
reason-phrase in turn is defined *<TEXT, excluding CR, LF>. I take this to mean that the second SP is absolutely required. This is very similar to problem 150, reported for Apache 1.1.1 in the bug database.
>How-To-Repeat:
See the full description
>Fix:
Ensure that there is always a space after the status-code, even if the reason-phrase is empty.
>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! ]