Closed
Bug 1254742
Opened 9 years ago
Closed 9 years ago
4XX Response headers from https://esfrontline.bugzilla.mozilla.org missing access-control-allow-origin
Categories
(bugzilla.mozilla.org :: Infrastructure, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: ekyle, Assigned: fubar)
Details
The esFrontLine service will happily respond to bad requests with 4XX errors, and it will include `access-control-allow-origin=*` in the response header. For some reason this header is stripped by the time it gets to the client.
This is terrible because if Firefox gets just one response (400 or not) without an `access-control-allow-origin` header, it will never send AJAX requests to that URL again. Firefox must be rebooted before more requests can be made.
Assignee | ||
Comment 1•9 years ago
|
||
should be all set. :ekyle, can you verify?
Assignee: nobody → klibby
Flags: needinfo?(klahnakoski)
Assignee | ||
Comment 3•9 years ago
|
||
awesome, sorry for the delay!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•9 years ago
|
||
now the header is missing again!
Reporter | ||
Comment 5•9 years ago
|
||
curl -i -X GET https://esfrontline.bugzilla.mozilla.org/
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 6•9 years ago
|
||
(In reply to Kyle Lahnakoski [:ekyle] from comment #5)
> curl -i -X GET https://esfrontline.bugzilla.mozilla.org/
hah, because I missed adding it to the https virtual server. the two were named differently on zeus.. time to tidy up...
anyways, it's on both now!
Assignee | ||
Updated•9 years ago
|
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•