Hunchentot intermittently returns HTTP 304 / HTTP 200 on HTTP HEAD
Closed this issue · 1 comments
phoe commented
With the hunchentoot easy acceptor, when testing a page with https://livejs.com/ enabled on Firefox, it seems that hunchentoot replies either with 304 Not Modified or with 200 OK. This tends to break live.js live reloading when HTTP 200 is returned in long bursts.
It seems that this behavior follows some sort of linear backoff since the HTTP 200 streaks become longer and longer over time (see the below screenshot). Is this configurable inside Hunchentoot? And, if yes, where?
phoe commented
PEBKAC, this was a Firefox caching issue rather than Hunchentoot's.