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

Missing Content-Type HTTP header when cache is enabled #1198

Closed
did opened this Issue Mar 13, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@did
Member

did commented Mar 13, 2017

No description provided.

@did did added the issue label Mar 13, 2017

@did did self-assigned this Mar 13, 2017

did added a commit that referenced this issue Mar 13, 2017

@lcx

This comment has been minimized.

Show comment
Hide comment
@lcx

lcx Mar 13, 2017

fix works on my test system

HTTP/1.1 200 OK
Server: nginx/1.10.3
Date: Mon, 13 Mar 2017 14:43:58 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Accept-Encoding
ETag: W/"1eb598b9be8c537efb129f11881c9409"
Cache-Control: max-age=0, private, must-revalidate
X-Request-Id: fef3b285-3d17-478b-a05e-1c6d8ec870d9
X-Runtime: 0.017537
X-Proxy-Cache: BYPASS

lcx commented Mar 13, 2017

fix works on my test system

HTTP/1.1 200 OK
Server: nginx/1.10.3
Date: Mon, 13 Mar 2017 14:43:58 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Accept-Encoding
ETag: W/"1eb598b9be8c537efb129f11881c9409"
Cache-Control: max-age=0, private, must-revalidate
X-Request-Id: fef3b285-3d17-478b-a05e-1c6d8ec870d9
X-Runtime: 0.017537
X-Proxy-Cache: BYPASS

@did did closed this Mar 14, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment