#8194 closed bug (duplicate)
Ajax code failure on Symbian WRT
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | high | Milestone: | 1.5.1 |
Component: | ajax | Version: | 1.5 |
Keywords: | Cc: | jaubourg | |
Blocked by: | Blocking: |
Description
The new Ajax code in 1.5 doesn't work inside the Symbian Web Runtime. (Whereas 1.4.4 and earlier worked fine.)
I have no means to really debug this, but Ajax requests immediately return with an error, with no request ever going out to the server.
Change History (8)
comment:1 Changed 12 years ago by
Cc: | jaubourg added |
---|---|
Component: | unfiled → ajax |
Owner: | set to [email protected]… |
Priority: | undecided → high |
Status: | new → pending |
comment:2 follow-up: 4 Changed 12 years ago by
Status: | pending → new |
---|
I'm doing something very simple, i.e.,
$.ajax({ type: "POST", url: "https://example.com/lars/cgi/example", complete: complete, cache: false, timeout: 30000 });
This worked fine in 1.4.4 and earlier. In 1.5, "complete" immediately fires with a status of "error", with no request being made to the server (nothing in the logs.)
No, I haven't tried the WIP version, but will do so now.
comment:4 Changed 12 years ago by
Replying to [email protected]…:
I'm doing something very simple, i.e.,
$.ajax({ type: "POST", url: "https://example.com/lars/cgi/example", complete: complete, cache: false, timeout: 30000 });This worked fine in 1.4.4 and earlier. In 1.5, "complete" immediately fires with a status of "error", with no request being made to the server (nothing in the logs.)
No, I haven't tried the WIP version, but will do so now.
What does it output if you add:
error: function( jqXHR, status, error ) { console.log( error ); }
If it's "No Transport", then that's probably because you're trying to do a cross-domain request while Symbian WRT doesn't support CORS. The fix for this kind of situation is to set jQuery.support.cors to true before attempting any ajax request.
comment:5 Changed 12 years ago by
Status: | new → pending |
---|
comment:6 Changed 12 years ago by
Status: | pending → new |
---|
I can confirm that setting
jQuery.support.cors = true;
fixes this regression.
comment:7 Changed 12 years ago by
Milestone: | 1.next → 1.5.1 |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
OK, so this is actually a duplicate. Thanks for having confirmed this, Lars.
Thanks for taking the time to contribute to the jQuery project by writing a bug report.
Can you somehow submit a reduced test case or provide information by other means e.g. detailing what exactly you are doing and what kind of ajax calls are being made.
Did you already try the jQuery WIP version as described in: How to report bugs to check if the bug hasn't already been fixed?