Opened 10 years ago
Closed 10 years ago
#13599 closed bug (notabug)
ajax automatic reponse mimetype parsing does not work properly when run from file://
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Priority: | undecided | Milestone: | None |
| Component: | unfiled | Version: | 1.9.1 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
If you run an ajax request to SERVER_URI without explicit dataType spec, the response normally is handled according to the returned mime-type (Content-Type http header). This does not seem to work when running the Website locally (with an ajax request to a remote server) from your filesystem (file:// protocol) in a current Firefox 19.0.2).
As you can imagine this causes weird, hard to track-down issues when the code is deployed on a server, as the behavior of jquery suddenly changes to autoparse depending on mimetype.
This issue seems to be related to (but not the same, as the ajax request is not local but to a fixed full URI): http://stackoverflow.com/questions/1828228/why-does-jquery-insist-my-plain-text-is-not-well-formed
Change History (2)
comment:1 Changed 10 years ago by
comment:2 Changed 10 years ago by
| Resolution: | → notabug |
|---|---|
| Status: | new → closed |
This seems pretty obvious to me. Sorry it took you a while to find it but if we added notes for every item that was pretty obvious the docs would be very hard to read.
#13600 is a duplicate of this ticket.