Side navigation
#11906 closed feature (patchwelcome)
Opened June 14, 2012 07:59AM UTC
Closed January 06, 2013 11:50PM UTC
ajax error on cross-domain-request
| Reported by: | fb@eye-on.de | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | None |
| Component: | ajax | Version: | 1.7.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
If you want to do an ajax-request to a different domain with jQuery ajax functions now, you only get "error" as response on error-callback-function.
it would be great to get a more detailed error-message like cross-domain-error or something like this, because sometimes it takes some time to realize that the problem is cross-domain related.
best regards
Frederic
Attachments (0)
Change History (5)
Changed June 26, 2012 01:39PM UTC by comment:1
| component: | unfiled → ajax |
|---|---|
| priority: | undecided → low |
| status: | new → open |
Changed September 09, 2012 01:10AM UTC by comment:2
| type: | enhancement → feature |
|---|
Bulk change from enhancement to feature.
Changed January 06, 2013 09:22PM UTC by comment:3
This is made more difficult by the heroic measures we use to try and get something to work, and the fact that not all supported browsers support features like CORS. At some point the developer needs to know the rules and follow them.
@jaubourg, if you think there are some ways to improve the error can you implement them? If not let's close this ticket.
Changed January 06, 2013 11:01PM UTC by comment:4
Well, you can still look at the jqXHR instance and inspect its status and responseText fields, though it won't give much info on browsers that do not support CORS.
I'd say let's close the ticket as patchwelcome... any attempt to make the error more meaningful will probably involve assumptions that will prove invalid in other situations but I could be proven wrong.
Changed January 06, 2013 11:50PM UTC by comment:5
| resolution: | → patchwelcome |
|---|---|
| status: | open → closed |
Sure, patchwelcome works for me. I'd warn anyone trying to tackle this that it is fraught with peril due to all the various browser issues. Whatever patch was submitted would need to be well tested and documented.