-
Notifications
You must be signed in to change notification settings - Fork 16
Expose ETag header #631
Comments
It seems to still be the case with Kinto 1.11.0 The ETag is exposed on the 200 status code but not on the 304. |
Ah, I remember Apache (but not Nginx) does the same (because just like a 304 is supposed not to repeat the body of the request, it also shouldn't repeat all the headers from the earlier 200 to which it refers). |
I have looked into it, but I am not sure how to plug cornice It seems to be what we did in reapply_cors which should be called on |
Which is probably called because the header is present. |
Ok I got it 🎱 Actually this happens with the default bucket only. $ http https://kinto.dev.mozaws.net/v1/buckets/beers/collections/barley/records/15ff09fd-1dbc-4556-9101-08b85f62f776 \
If-None-Match:'"1454075102101"' \
--auth user:pass HTTP/1.1 304 Not Modified
Access-Control-Expose-Headers: Content-Length, Expires, Alert, Retry-After, Last-Modified, ETag, Pragma, Cache-Control, Backoff
Connection: keep-alive
Date: Fri, 29 Jan 2016 13:45:27 GMT
ETag: "1454075102101"
Last-Modified: Fri, 29 Jan 2016 13:45:02 GMT
Server: nginx |
This is because |
This is a Kinto problem, related to the default bucket. |
Moved ``utils.current_service(request)`` to reified request method (ref #631)
Looking at
cliquet/cliquet/__init__.py
Lines 98 to 99 in 59fca2d
The text was updated successfully, but these errors were encountered: