4 ms·
Oh, interesting :/ Is it the same on "new-hn.algolia.com"? (we removed the HTTP OPTION query that was performed to deal with extra headers & CORS -> maybe it di
by redox_ 12y ago
Oh, interesting :/ Is it the same on "new-hn.algolia.com"? (we removed the HTTP OPTION query that was performed to deal with extra headers & CORS -> maybe it didn't help).
- Poiesis 12y agoI can access new-hn though I can't say whether it's due to your changes. The https redirect adds an extra step because of a click through "this site could be evil" that Websense adds--I think it stores the acceptance for the http site, but then the https redirect happens which isn't registered on the "possibly evil" click through acceptance list so it initially fails. Manually going to the https version fixes this problem, though. Man, I hate proxies.