Closed Bug 236164 Opened 22 years ago Closed 22 years ago

HTTP POST hangs between header and body

Categories

(Core :: Networking, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: bradley.vender, Assigned: darin.moz)

References

()

Details

User-Agent: Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8 We're using a simple custom HTTP server which does a rough job of implementing POST and GET methods. What we are expecting is POST ..... rest of POST header POST body What we are getting is that Mozilla 1.5 and Firefox 0.8 stop between the header and the body. There are no Expect elements in the POST header, and nothing short of sending an error header and closing the connection without receiving the POST body seems to produce a result (and doesn't do any good since then we haven't received the POST body). Reproducible: Always Steps to Reproduce: 1. Bring up http://vcell.ndsu.nodak.edu:8101/mozilla-test/ 2. Click on submit form button 3. Observe the spinning logo button until the connection times out. Actual Results: The server receives the following data: POST /mozilla-test/ HTTP/1.1 Host: vcell.ndsu.nodak.edu:8101 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8 Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Referer: http://vcell.ndsu.nodak.edu:8101/mozilla-test/ Content-Type: application/x-www-form-urlencoded Content-Length: 25 Expected Results: The server should have received the body of the POST after the POST header.
Installed ethereal to look at traffic, and server is indeed being sent the POST body. User error.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
V
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.