Closed
Bug 721311
Opened 12 years ago
Closed 12 years ago
Error 400 gateway.php with flex
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 724465
People
(Reporter: jonathan.herelier, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0a1) Gecko/20120125 Firefox/12.0a1 Build ID: 20120125064912 Steps to reproduce: I click on a link that opens a new tab to open my flex application. The application starts but fails to load gateway.php. This script allows you to manage PHP services with flex. Actual results: The application opens but does not load completely because it was time data services PHP and Firebug returns me a 400 error for the file gateway.php (This is the firebug message : Bad Request - Invalid Header HTTP Error 400. The request has an invalid header name.) Expected results: The application should load in full. I should point out that the same application works with Firefox 9 and Aurora 11
Comment 1•12 years ago
|
||
Please provide a testcase
Reporter | ||
Comment 2•12 years ago
|
||
Hi, I put a test (an HelloWorld) on an Apache server, you can try this at http://testflexphp.franceserv.com/TestPhpService.html, and it works, but the same test on my IIS server doesn't work (and it doesn't work only with nightly 12.0 ). I can't give you an access to the IIS server because I don't have a public IP. How can I give you the source code so you can make tests ? I'm sorry but it's my first time that I report a bug.
Comment 3•12 years ago
|
||
Jonathan: Please open about:config (as URL in FF), confirm the warning, enter "referer" in the top filter bar and change the value of "network.http.sendRefererHeader" from "2" to "1" or "0" and try it again.
Reporter | ||
Comment 4•12 years ago
|
||
I tested with two values (1 and 0) and both work on Aurora 12.0a2 and Nightly 13.0a1. Thank you. (In reply to Matthias Versen (Matti) from comment #3) > Jonathan: > Please open about:config (as URL in FF), confirm the warning, enter > "referer" in the top filter bar and change the value of > "network.http.sendRefererHeader" from "2" to "1" or "0" and try it again.
Comment 5•12 years ago
|
||
Thanks for confirming the issue. I could mark it as depending on bug 410904 or mark it as dupe of bug 724465 I will dupe it to bug 724465
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•