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

ETag headers #129

Open
ataylorme opened this issue Jan 16, 2019 · 2 comments
Open

ETag headers #129

ataylorme opened this issue Jan 16, 2019 · 2 comments
Labels

Comments

@ataylorme
Copy link

The ETag header is " an identifier for a specific version of a resource. It allows caches to be more efficient, and saves bandwidth, as a web server does not need to send a full response if the content has not changed."

Pantheon supports Etag headers but WordPress does not add them by default. Advanced Page Cache could improve caching of WordPress sites on Pantheon by adding proper ETag headers.

@danielbachhuber
Copy link
Contributor

For normal pages, this isn't easily possible because WordPress doesn't know what data is present on the page.

In the REST API context, this should be possible.

@ataylorme
Copy link
Author

It probably makes sense to use ETag headers on cached REST API responses

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants