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

Make ETag header comply with standard. #2603

Merged
merged 1 commit into from
Oct 30, 2016

Conversation

kentonv
Copy link
Contributor

@kentonv kentonv commented Jun 30, 2016

The standard says that an ETag must be surrounded in double quotes:

https://tools.ietf.org/html/rfc7232#section-2.3

Although browsers tend to be lenient, omitting the quotes can confuse/break some kinds of proxies and other tools that demand compliant formatting. For example, Sandstorm.io enforces strict HTTP usage for security reasons and will block responses with invalid ETags.

The standard says that an ETag must be surrounded in double quotes:

https://tools.ietf.org/html/rfc7232#section-2.3

Although browsers tend to be lenient, omitting the quotes can confuse/break some kinds of proxies and other tools that demand compliant formatting. For example, Sandstorm.io enforces strict HTTP usage for security reasons and will block responses with invalid ETags.
@kentonv
Copy link
Contributor Author

kentonv commented Jun 30, 2016

Oops, updated tests -- now fails at the same place that it fails on the master branch.

@ocdtrekkie
Copy link

ocdtrekkie commented Jul 30, 2016

Apparently this is the issue that has been haunting me since February 25th of this year and I didn't know it.

@darrachequesne darrachequesne merged commit d026c00 into socketio:master Oct 30, 2016
@darrachequesne
Copy link
Member

Thanks!

@darrachequesne darrachequesne added this to the 1.6.0 milestone Nov 20, 2016
dzad pushed a commit to dzad/socket.io that referenced this pull request May 29, 2023
The standard says that an ETag must be surrounded in double quotes:

https://tools.ietf.org/html/rfc7232#section-2.3

Although browsers tend to be lenient, omitting the quotes can confuse/break some kinds of proxies and other tools that demand compliant formatting. For example, Sandstorm.io enforces strict HTTP usage for security reasons and will block responses with invalid ETags.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants