You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Wade Oberpriller <ob...@network.com> on 1999/10/26 00:57:33 UTC
protocol/5196: Server response missing Header for 400 Bad Request
>Number: 5196
>Category: protocol
>Synopsis: Server response missing Header for 400 Bad Request
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Mon Oct 25 17:10:02 PDT 1999
>Last-Modified:
>Originator: oberpwd@network.com
>Organization:
apache
>Release: 1.3.3
>Environment:
SunOS nsplab14 5.6 Generic_105181-12 sun4u sparc SUNW,UltraSPARC-IIi-Engine
>Description:
Sending a POST message with a missing resource (POST HTTP/1.1), and the server
responds with HTML markup and no header. The markup looks like such:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>400 Bad Request</TITLE>
</HEAD></BODY> ....
Tested this versus a Microsoft Web server and it behaved correctly.
>How-To-Repeat:
nsplab14.network.com
>Fix:
>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! ]