I created a test case which resides at www.lasguerrillas.com/testcase.xhtml (so that it has the privaleges to do an XMLHttpRequest).
What are the expected and actual results for your testcase?
Expected results are similar to when the page is loaded: an alert with the text returned from the database should have // SOME DATE students.push("SOME NAME,SOME PHONE"); drivers.push("SOME NAME,SOME PHONE"); With several students.push() and drivers.push() In reality, when the request is sent again, the server does not recieve the second http_request.send() so the alert contains just: //
In Opera (and Firefox 1.5.1) at www.lasguerrillas.com/testcase.xhtml I get an alert when I load with: //2006-02-26 drivers.push('Dan,'); students.push('Francois,'); students.push('Ling,248 346 5903'); students.push('Francois,'); If I click on any of the two buttons at the top, I get something like this: //2006-02-27 drivers.push('Dan,'); drivers.push('Cathy Gilbert,248-320-3477'); students.push('trevor,2487093145'); students.push('Robert Liu,248-540-1647'); students.push('Robert Liu,248-540-1647'); students.push('Francois,'); students.push('Francois,'); students.push('Ling,248 346 5903'); students.push('Trevor,248-709-3145'); students.push('Ryan Gilbert,248-860-5627'); In this build though, clicking on any of the links returns: // Which means that the date for which it is retrieving data, which should be following the "//", is not being received by the php scrip ONLY in this build. On top of that, I get errors every once in a while: "Method Not Implemented date=2006-02-28GET to /testcase.xhtml not supported. Invalid method in request date=2006-02-28GET /testcase.xhtml HTTP/1.1 Apache/1.3.33 Server at www.lasguerrillas.com Port 80" From the server, which suggests that SOMETHING in firefox is at fault.
Those errors look like server errors to me, not Firefox errors. Are you saying that you have a Firefox build that works, and one that doesnt? What are the build IDs of the two builds, if so? Could you use the builds at ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly and http://archive.mozilla.org/pub/firefox/nightly/ to narrow down a regression range?
The unworking one is contained in the original bug request and was a nightly (downloaded yesterday). The working one is: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20060111 Firefox/22.214.171.124 I'm running the nightly off my flash drive, and the working one is installed on my computer normally.
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla1.8/firefox-1.5.en-US.win32.zip Is the build I downloaded yesterday around 2:30PM.
Great, thanks for finding a regression range! Are you able to reproduce this consistently? Could you possibly test the same code on another server? The only bug I see that could affect this and that landed in that range is bug 137155, and that might have affected certain server but not others.
Creating an HTTP log per the instructions at http://www.mozilla.org/projects/netlib/http/http-debugging.html and attaching it to this bug as an attachment might also be useful in finding the cause of the problem.
I did some analysis, and it looks like in older versions, the http_request.send() is sent as a seperate packet, whereas in the newer builds, it's sent in the same packet. Therefore, it may or may not be a result of confusing the server, although as an apache server, it should be able to handle what are appropriate transmissions.
Component: General → Networking: HTTP
Product: Firefox → Core
QA Contact: general → networking.http
Version: unspecified → Trunk
This sounds like a server bug to me. You cannot make any assumptions about how a TCP stream might be broken into packets. The HTTP requests from the browser appear to be perfectly valid HTTP/1.1 requests, so I think bug is invalid.
12 years ago
Closing this as invalid per above comment
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.