s / s.js have problems loading

[Glamdring]

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.

[homakov]

When I visit cobased.com:

Creating Application Cache with manifest https://securelogin.pw/s.appcache
(index):1 Application Cache Checking event
(index):1 Application Cache Downloading event
(index):1 Application Cache Progress event (0 of 2) https://securelogin.pw/s.appcache
(index):1 Application Cache Progress event (1 of 2) https://securelogin.pw/s
sdk.js:17 ext
(index):1 Application Cache Progress event (2 of 2) 
(index):1 Application Cache Cached event

can you post your log with chrome?

[Glamdring]

I tried both at home and at work, and it fails in both cases with both browsers. Here's Chrome's console:

Document was loaded from Application Cache with manifest https://securelogin.pw/s.appcache
(index):1 Application Cache Checking event
s:1 GET https://securelogin.pw/s.js net::ERR_FAILED
(index):1 Application Cache NoUpdate event

Possibly related:

• on cobased.com clicking the login button without the plugin installed opens securelogin.pw (correct behaviour).
• on https://passport-securelogin.herokuapp.com/ the following opens:

This site can’t be reached

The webpage at chrome-extension://abpigncghjblhknbbannlhmgjpjpbajj/index.html might be temporarily down

In my project where I'm testing, the behaviour is the same as on the nodejs (Heroku) demo.

[Glamdring]

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.
Likely something related to the browser cache.

[Glamdring]

Some more info: when I request the cache file, I get a warning in Chrome:

Resource interpreted as Document but transferred with MIME type text/cache-manifest: "https://securelogin.pw/s.appcache".

Also, not sure if intended, but s.js is not present in the cache file.

[homakov]

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

[Glamdring]

Another possibly related error I just noticed in my console:

securelogin.pw/s Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

[homakov]

BLOCKED BY CLIENT could be an ad blocker?

[Glamdring]

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