Response title
This is preview!
Move this topic
GET Status 0 on local page load with Cordova
in jQuery Mobile
•
1 year ago
I am using jqm with Cordova. When a local page loads jqm uses GET but returns the content along with a status of 0. This is seen in the logging app I am using as an error (it was expecting a status = 200 for a GET).
I saw this item in the docs but it did not make any difference:
- $.ajaxPrefilter( function(options, originalOptions, jqXHR) {
- if ( applicationCache &&
- applicationCache.status != applicationCache.UNCACHED &&
- applicationCache.status != applicationCache.OBSOLETE ) {
- // the important bit
- options.isLocal = true;
- }
- });
1
Replies(9)
Your local filesystem is not a server.
"error codes" from local filesystem access are likely browser-dependent.
Google shows lots of results for this search, though they seem to involve various contexts. But almost all relating to Ajax, which is how JQM normally fetches it's pages.
I'd suggest asking on a Cordova forum, where you are more likely to get an answer. I see solutions suggesting you check for status of 0 with content length of 0 to detect an error.
It would see odd, though, to get errors when you are fetching static files from your app's filesystem. It means you forgot to include a file!
Maybe there is some Cordova plugin to make the filesystem act more like a server.
Leave a comment on watusiware's reply
Everything I see is normal ajax calls vs what jqm is doing under the covers, but the same code run as a webpage in Mobile Safari does not cause the alert so it is definitely caused by the combination of the two, or embedded in how Cordova is handling these local URL's.
I will try to post the same question in a Cordova forum but I suspect the response will be that this is a jqm issue. 
Leave a comment on ccouper's reply
You still haven't said what "the logging app I am using is".
THAT would see to be the most likely place where the trouble is, as multiple sources suggest that some browsers/webviews will return an error code of 0 rather than 200 in certain circumstances - and so you should check the content length to see if it is really an error.
Do you have any problem if you do not use the unnamed logging app?
We can't guess how JQM or Cordova interacts with unknown scripts.
You can easily eliminate JQM as a source of the problem by making a simple HTML page and making an Ajax request using jQuery (or with DOM methods).
Exactly what is the undesired behavior? Page doesn't load? Logging app erroneously logs an error when there is no error? Something else?
Leave a comment on watusiware's reply
You still haven't said what "the logging app I am using is".Didn't notice that request in your first post
I contacted the author but have not heard anything back from them.
Just a simple page request will cause the error:
- <li data-icon="false"><a href="overview.html"><img src="css/images/white/896-road-sign.png"/>Getting Started</a></li>
The only undesired behavior is the log is filling up with needless entries because everything works OK, but the log sees these status 0 returns as errors. It then posts them as errors.
Leave a comment on ccouper's reply
Since it is a licensed product, I would hold their feet to the fire. They are logging as an "error" something that is not an error.
The error code comes from the browser, not from jQuery Mobile.
JQM just makes an Ajax request for each page. The error code from the browser is the error code from the browser, and JQM has no way of changing that.
I looked at their documentation - but there's precious little of it, and doesn't seem to be any way to control which errors are logged and which are not.
Does it do the same on both iOS and Android?
Leave a comment on watusiware's reply
Since the client is in js I just downloaded it. Giving it a quick look it appears that it is supposed to handle this situation:
- function logNetwork(success) {
- try {
- var info = xhr._additionalInfo || {},
- networkOptions = logger.options.network;
- info.status = xhr.status || 0;
- info.statusText = xhr.statusText || '';
- if (logger.options.network.logResponse) {
- info.response = xhr.responseText;
- try {
- info.responseHeaders = xhr.getAllResponseHeaders();
- } catch (e) {
- info.responseHeaders = {};
- }
- }
- var codeAllowed = (networkOptions.codes.indexOf(xhr.status) >= 0) ||
- (!networkOptions.codes.length && (networkOptions.codesExclude.indexOf(xhr.status) < 0)),
- // XHR could return 0 status on a success call, when requesting local file protocol.
- // We assume it is equal with 200 response code
- successWithZeroStatus = success && !info.status && (networkOptions.codes.indexOf(200) >= 0);
- if (networkOptions.enabled && (codeAllowed || successWithZeroStatus)) {
- logger.network(info);
- }
- } catch (e) {
- }
- }
- I'll play with it a bit to see what that is not working for me.
Leave a comment on ccouper's reply
Does it do the same on both iOS and Android
It does not seem to have the issue with Android, but I only tested one device. I also only tested it on iOS 11 too. Other versions may not exhibit the problem.
Leave a comment on ccouper's reply
I can't guess what is in logger.options.network structure, specifically codes and codesExclude.
Only on iOS is consistent with my Google search results. This has been widely-reported, and multiple projects have implemented a work-around.
You need to press the publisher of your paid logging product to fix their product. Or find one that works correctly.
Leave a comment on watusiware's reply
I am not sure what the original logic was supposed to be the codes array is empty so ...
I modified it thusly and it seems to work fine now:
- var codeAllowed = (networkOptions.codes.indexOf(xhr.status) >= 0) ||
- (!networkOptions.codes.length && (networkOptions.codesExclude.indexOf(xhr.status) < 0)),
- // XHR could return 0 status on a success call, when requesting local file protocol.
- // We assume it is equal with 200 response code
- successWithZeroStatus = success && !info.status ;
- if (networkOptions.enabled && (codeAllowed && !successWithZeroStatus)) {
- logger.network(info);
- }
Leave a comment on ccouper's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic
Reply to ccouper's question