js/assets.js:435 (onRemoteFileError)

[ghost]

tested with latest commit aka this one d94be2854a68c2cff7b528d2f103a058eaf97296

Thanks.

PS: really appreciate your work & dedication

[gorhill]

Network issues. Did you check if the remote server can be reached? See the extension dev console to find out which asset could not be fetched.

[ghost]

I don't actually know where to find that extension dev console ... if it's Ctrl+Shift+J it seems that I should be on a specific tab.

[gorhill]

1. chrome://extensions
2. Developer mode
3. Click "background.html" for HTTPSB
4. The same error messages should be there, except the %s will be properly expanded

[ghost]

Thank you. I had no idea that was anything useful.

My fault, apologies:

 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
https://raw.githubusercontent.com/gorhill/httpswitchboard/master/assets/checksums.txt?httpsb=1411351321614 
assets.js:435 HTTP Switchboard> readRemoteFile() / onRemoteFileError("assets/checksums.txt")assets.js:435 onRemoteFileError
traffic.js:923 HTTP Switchboard> Beginning to intercept net requests at 2014-09-22T02:02:02.206Z

EDIT: I had XHR allowed for raw.githubusercontent.com guess network issues then EDIT2: actually says blocked by client, must mean some other extension was doing it

[gorhill]

This should not be blocked, there is a hard-coded exception in HTTPSB for this, to prevent HTTPSB from blocking itself.

Does this work from your end: https://raw.githubusercontent.com/gorhill/httpswitchboard/master/assets/checksums.txt?httpsb=1411351321614 ?

[ghost]

yes it works like that, in the address bar

[gorhill]

Ok so it's working now?

[ghost]

I guess, but I don't know when httpsb tries to access that again if it works, can I force it? maybe browser restart?

[gorhill]

Going to the About tab in the dashboard should cause HTTPSB to download the checksums, if I remember correctly.

[ghost]

looks like it only fails on startup, but I'm sure it's because of this other simple extension that I'm using http://sourceforge.net/p/footab/code/ci/master/tree/src/background.js

because it seems to happen only when I leave a tab with HTTPSB settings open (even if not on About page)

ok wait I'll just disable it... yep that's the one

[gorhill]

Yes, looks like that extension is not checking whether the request is a behind-the-scene one or not. It should let the behind-the-scene request go through unblocked.

[ghost]

the weird thing is that even after everything is done loading, after startup, and I click Options on HTTPSB's extensions page, it still shows as blocked, first time, until I open Options again In other words, when I open About the first time: An error occurred. Is XHR blocked for raw2.github.com? and then, and subsequent times it works. Probably related to the way FooTab extension works, maybe + the fact that it blocks somehow the Options page just like it does any other tab which kinda implies that this Options page is loaded by HTTPSB on chromium startup and not when clicking Options.