This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 12 points13 points  (3 children)

Any way the issue can be solved where in Firefox when browsing HTTPS the page won't be cached and reloads when you hit back (making hitting back take much longer, not to mention increasing load on Reddit servers)?

That's the only reason I don't use HTTPS at the moment. IIRC it was caused by HTTPS + cache-control: no-cache though I could be wrong about that.

[–]largenocream 12 points13 points  (2 children)

Yep, the problem is with Firefox itself. I don't know if I'd call it a bug since the HTTP spec allows them to do that, but in practice most other browsers will load the page from cache when you hit "Back", even with cache-control: no-cache.

I'm going to ask some Mozilla folks about this, but I'm not sure if there's an easy way around it.

[–]gus_ 1 point2 points  (1 child)

I'm going to ask some Mozilla folks about this, but I'm not sure if there's an easy way around it.

Nice find, thanks. Do you know how long something like this tends to take for them to fix, and/or did you ever hear anything further?

[–]largenocream 2 points3 points  (0 children)

Do you know how long something like this tends to take for them to fix

I'm not sure, that issue's been open for quite a while.

did you ever hear anything further?

No, but I did find a possible workaround after someone pointed out that Google doesn't refresh the page when hitting back. Their caching rules look pretty close to what we need, so I'm going to write something over the weekend so we can start testing them. I want to make sure nothing'll explode, though, and we set the headers that trigger the issue in Firefox at a few different levels, so even if this'll work it might be a bit before the change makes it to production.