Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add support for private cache-control flag #373

Closed
kpdecker opened this issue Jan 10, 2013 · 4 comments
Closed

Add support for private cache-control flag #373

kpdecker opened this issue Jan 10, 2013 · 4 comments
Assignees
@hueniverse
Labels
feature New functionality or improvement
Milestone
0.12.0

Comments

@kpdecker
Copy link
Contributor

No description provided.

@hueniverse
Copy link
Contributor

Example response header?

@kpdecker
Copy link
Contributor Author

max-age=120, must-revalidate, private

@hueniverse
Copy link
Contributor

When do you set private? Is it for a given endpoint? the entire server? only when using authentication (header or cookie)?

@kpdecker
Copy link
Contributor Author

The root and config endpoints should only be cached by the final client not any proxies between here and there.

@ghost ghost assigned hueniverse Jan 12, 2013
hueniverse pushed a commit that referenced this issue Jan 26, 2013
closes #373
7c60ddb
@hueniverse hueniverse mentioned this issue Jan 28, 2013
Merged
jmonster pushed a commit to jmonster/hapi that referenced this issue Feb 10, 2014
closes hapijs#373
5c990ae
@lock lock bot locked as resolved and limited conversation to collaborators Jan 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@hueniverse hueniverse

Labels
feature New functionality or improvement
Projects
None yet
Milestone
0.12.0
Development

No branches or pull requests
2 participants
@hueniverse @kpdecker