On 14.11.17 16:42, Artur Pedziwilk wrote:
Works OK on my Safari Version 11.0.1 (13604.3.5) and macOS 10.13.1 (17B48).
Same versions here, but Relay Search does not work for me. URLs that are supposed to show node details don't work either, only the broken query page is shown. I tested this both with existing Atlas bookmarks and URLs copied over from Chrome.
-Ralph
I have since removed all cookies and data tied to the torproject.org domain from my Safari 11 cache, and now Relay Search seems to work as designed. I'm glad, of course, but it still seems weird. At least I have screenshots to prove that I did not merely imagine the problems. ;-)
-Ralph
Hi,
On 14/11/17 16:04, Ralph Seichter wrote:
I have since removed all cookies and data tied to the torproject.org domain from my Safari 11 cache, and now Relay Search seems to work as designed. I'm glad, of course, but it still seems weird. At least I have screenshots to prove that I did not merely imagine the problems. ;-)
Thanks for following up. (:
I think there may be some issues, with such a large change some breakage may occur if you have different versions of the JavaScript files and the templates in your cache.
The Last-Modified dates seem to work, and If-Modified-Since seems to work too. Maybe Safari is just doing something weird and not invalidating the cache.
Thanks, Iain.
On 15 Nov 2017, at 03:12, Iain R. Learmonth irl@torproject.org wrote:
I think there may be some issues, with such a large change some breakage may occur if you have different versions of the JavaScript files and the templates in your cache.
The Last-Modified dates seem to work, and If-Modified-Since seems to work too. Maybe Safari is just doing something weird and not invalidating the cache.
The canonical way to solve this issue is to use a cache-breaker parameter in the resource URL.
So your current resource references probably look like: https://atlas.torproject.org/resource.js
But a cache-breaker would look like: https://atlas.torproject.org/resource.js?v1.1
Then when you change any code in the file, you update the version: https://atlas.torproject.org/resource.js?v1.2
This usually doesn't require any web server support, because the parameter is ignored by the server, which serves the most recent version regardless. It's just there to tell the cache that the code has been updated.
Of course, this is annoying to update if your site embeds a reference to the resource on every page, rather than listing URLs in a config.
T
tor-relays@lists.torproject.org
-
Iain R. Learmonth -
Ralph Seichter -
teor