Closed jabooth closed 9 years ago
This must be something to do with Application Cache. Here's what I see on a first visit in the console.
www.landmarker.io/:1 Creating Application Cache with manifest http://www.landmarker.io/lmio.appcache www.landmarker.io/:1 Application Cache Checking event www.landmarker.io/:1 Application Cache Downloading event www.landmarker.io/:1 Application Cache Progress event (0 of 5) http://www.landmarker.io/css/help-8da0a165.css www.landmarker.io/:1 Application Cache Progress event (1 of 5) http://www.landmarker.io/index.html www.landmarker.io/:1 Application Cache Progress event (2 of 5) http://www.landmarker.io/css/landmarker-6ab08838.css www.landmarker.io/:1 Application Cache Progress event (3 of 5) http://www.landmarker.io/img/cursor.png www.landmarker.io/:1 Application Cache Progress event (4 of 5) http://www.landmarker.io/bundle-2052f37e.js www.landmarker.io/:1 Application Cache Progress event (5 of 5) www.landmarker.io/:1 Application Cache Cached event http://localhost:5000/api/v1/mode Failed to load resource: net::ERR_CONNECTION_REFUSED
and then second time around:
Document was loaded from Application Cache with manifest http://www.landmarker.io/lmio.appcache (index):1 Application Cache Checking event (index):1 Application Cache NoUpdate event index.js:35 Successfully found mode: mesh
Note that this wasn't to do with the application caching at all. It was a result of moving from url query seperators ? to #.
?
#
This must be something to do with Application Cache. Here's what I see on a first visit in the console.
and then second time around: