'/signin' is dynamic and has no cache headers #168

Closed
lloyd opened this Issue Mar 25, 2013 · 1 comment

Projects

None yet

1 participant

@lloyd
Contributor
lloyd commented Mar 25, 2013

We've already seen that android 2.x's built in browser will aggressively cache documents served without any cache headers.

/sign_in varies by user (its a template and the current authenticated user is embedded in it) - so serving it without any cache headers may cause issues (at the best, an extra authentication on android, at the worst, our stuff might break and stay broken until the user figures out how to force a cache refresh).

@lloyd
Contributor
lloyd commented Mar 25, 2013

PR merged.

@lloyd lloyd closed this Mar 25, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment