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

If-None-Match header not sent by Chrome #208

Open
dcoraboeuf opened this issue Jan 3, 2015 · 2 comments
Open

If-None-Match header not sent by Chrome #208

dcoraboeuf opened this issue Jan 3, 2015 · 2 comments
Labels
gui type: bug Defect issue

Comments

@dcoraboeuf
Copy link
Contributor

The ETag has been introduced for issue #178 in order to allow an efficient caching on client's side.

The ETag header is correctly sent by the server, but the corresponding If-None-Match request header is not sent by Chrome, although it is sent correctly by Firefox.

After a first quick investigation, it seems to be a common problem in Chrome.
@dcoraboeuf dcoraboeuf added type: bug Defect issue gui labels Jan 3, 2015
@dcoraboeuf dcoraboeuf mentioned this issue Jan 3, 2015
Closed
@Ale763
Copy link

Ale763 commented Apr 28, 2019

Is this bug solved? I'm having this issue on Chrome and Canary on OSX 10.14.4.
The ETag is set, but the browser does not request with If-None-Match. In Firefox this header is set.

@dcoraboeuf
Copy link
Contributor Author

I did not test this recently. I'm not sure how this could be solved at code level ; if you have any idea, that'd be great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
gui type: bug Defect issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dcoraboeuf @Ale763