-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
s / s.js have problems loading #40
Comments
When I visit cobased.com:
can you post your log with chrome? |
I tried both at home and at work, and it fails in both cases with both browsers. Here's Chrome's console:
Possibly related:
In my project where I'm testing, the behaviour is the same as on the nodejs (Heroku) demo. |
Okay, some progress - after a restart and opening Chrome again, it works fine the first time. the "s" files are loaded and clicking the button opens securelogin.pw (if no plugin installed). After that it starts failing again. |
Some more info: when I request the cache file, I get a warning in Chrome:
Also, not sure if intended, but s.js is not present in the cache file. |
Maybe something happened to appcache. There are long term plans by w3c to remove appcache entirely. So we should do it too I guess just in case. will do |
Another possibly related error I just noticed in my console:
|
BLOCKED BY CLIENT could be an ad blocker? |
Quite possibly, I do have ABP on Chrome. But why would it recognize it as an add, maybe because of the short name? Note: the original issue (the ERR_FAILED) is not related to ABP, because I don't have it at work and it still happens |
In the developer tools I always see problems with /s or /s.js . In Chrome the problem is (failed) "ERR_FAILED", and on Firefox it's just stuck, never loading.
When I open /s separately, it works. But on the demo pages the above behaviour is observed.
The text was updated successfully, but these errors were encountered: