window.applicationCache is undefined in Chrome 70 / Firefox 63 about pylon

[exsilium]

Hi and thanks for the bug report - what steps are needed to reproduce this? Are you running in offline mode? I'm on FF Quantum 63 and Chromium 70 - haven't noticed this issue yet but I'll try to repro. Thanks!

[mchen6]

Thanks for your notice.

I clone pylon repo and npm i, then launch it on my Ubuntu 16.04 box with below command:

./bin/pylon.sh -w ~/tmp -l 10.0.0.130

Then on my Win10 x64 machine I visited http://10.0.0.130:3131/ with Chrome 70 and FF Quantum 63, the same error can be reproduced. I think I was not in offline mode.

Hi and thanks for the bug report - what steps are needed to reproduce this? Are you running in offline mode? I'm on FF Quantum 63 and Chromium 70 - haven't noticed this issue yet but I'll try to repro. Thanks!

[exsilium]

Thank you for the details. I'll try to reproduce this. Can you also please add your node and npm versions? Thanks!

[mchen6]

My node and npm versions are v8.12.0 and 6.4.1 respectively. Thanks.

[mchen6]

It seems appCache has been diabled on non-secure connection:
https://www.chromestatus.com/feature/5714236168732672
https://www.thesslstore.com/blog/firefox-require-https-appcache/

To verify this, I added an nginx secured proxy in front of pylon, and confirmed this issue has disappeared.

[exsilium]

Thanks for digging into this more. All my test instances are also behind nginx so that explains why I wasn't able to reproduce this. I'll look into this in more detail...

Using via localhost also doesn't disable the appCache. To reproduce, Pylon needs to be bound via -l flag to an external IP and browser should be used to access that IP via unsecured socket. appCache is used in ext.offline/lib-offline.js

[mchen6]

It now works fine on development branch. Closing issue. Thanks.