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.

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

Recommend use of the Vary header in version 2 of the Users Guide #323

Open
ghobona opened this issue Nov 30, 2022 · 2 comments
Open

Recommend use of the Vary header in version 2 of the Users Guide #323

ghobona opened this issue Nov 30, 2022 · 2 comments
Labels
2022-11 Sprint Guide Part 1 Applicable to Part 1 Core

Comments

@ghobona
Copy link
Contributor

ghobona commented Nov 30, 2022

During the 2022-11 Web Mapping Code Sprint, there was feedback that to prevent the server from caching responses in some cases, it might be necessary to use the Vary header.

@ghobona
Copy link
Contributor Author

ghobona commented Nov 30, 2022

@jerstlouis Please elaborate.

@jerstlouis
Copy link
Member

For resource end-points that may return a different representation for the content encoded differently based on request headers, any header value should be included as part of a Vary: response header.
e.g., Vary: Accept, Accept-Encoding, Prefer

This will avoid issues with proxying / caching.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2022-11 Sprint Guide Part 1 Applicable to Part 1 Core
Projects
Development

No branches or pull requests

2 participants