You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Jacob Schroeder <js...@becomsys.de> on 1999/02/01 11:58:37 UTC
protocol/3806: 100-continue is not send on errors (see also PR#3575)
>Number: 3806
>Category: protocol
>Synopsis: 100-continue is not send on errors (see also PR#3575)
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Mon Feb 1 05:10:00 PST 1999
>Last-Modified:
>Originator: jschroeder@becomsys.de
>Organization:
apache
>Release: 1.3.4
>Environment:
Linux catilina.becomsys.de 2.0.36 #4 Fri Nov 20 12:03:23 MET 1998 i586 unknown
>Description:
If I send a POST request including an Expect: 100-continue header, but
without transmitting the message body to a
none-existing CGI-Skript, apache sends neither a 100 (Continue) nor a
404 (Not Found) response. It waits until it has read the entity-body
completely and sends the 404 response then. This clearly violates chapter
8.2.3 (first server requirement) of the rev 6 of the HTTP/1.1 draft.
100-continue works pretty well, if the resource exits.
Example:
client->server
POST /cgi-bin/test-cgi2 HTTP/1.1
Host: server.localnet:8080
Connection: close
Content-Type: text/plain
Content-Length: 11
Expect: 100-continue
<empty line>
server->client:
<nothing>
client->server:
Hello World
server->client:
HTTP/1.1 404 Not Found
Date: Mon, 01 Feb 1999 10:44:15 GMT
Server: Apache/1.3.4 (Unix)
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html
<empty line>
11c
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>404 Not Found</TITLE>
</HEAD><BODY>
<H1>Not Found</H1>
The requested URL /cgi-bin/test-cgi2 was not found on this server.<P>
<HR>
<ADDRESS>Apache/1.3.4 Server at linux4.localnet Port 8080</ADDRESS>
</BODY></HTML>
0
>How-To-Repeat:
see above
>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 leave the subject line UNCHANGED. This is not done]
[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! ]