#8152 closed bug (fixed)
Local ajax requests through chrome-extension:// protocol are not working
Reported by: | anonymous | Owned by: | jaubourg |
---|---|---|---|
Priority: | low | Milestone: | 1.5.1 |
Component: | ajax | Version: | 1.5 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Change History (4)
comment:1 Changed 12 years ago by
Component: | unfiled → ajax |
---|---|
Milestone: | 1.next → 1.5.1 |
Owner: | set to jaubourg |
Priority: | undecided → low |
Status: | new → assigned |
comment:2 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:3 Changed 12 years ago by
I marked this as fixed seeing as I applied the same tricks for the chrome-extension protocol as was in place for file. However, I cannot test it so I'd very much appreciate if somebody could confirm or infirm the fix, in which case I'll set up a test environment to look a little further.
comment:4 Changed 12 years ago by
I met a similar problem today. My browser is firefox 4.0pre11. I run the following code in "chrome://helloworld/content/index/index.html"
$.ajax({
type:"GET", url: "kkkmhDatabase.xml", dataType: "xml", success: function(xmlResponse){
alert("success");
}, error: function(jqxhr){
alert("error");
}
});
Both 1.4.4 and 1.5 will alert error.
Note: See
TracTickets for help on using
tickets.
Fixes #8152 by applying the same special cases for protocol "chrome-extension:" as were for "file:" (needs tests). Re-organizes and fixes the handling of special cases for HTTP status code in the xhr transport. Also re-organizes the handling of document.location in ajax.js.