Hello!
Using Postman i wanted to check the Etag mechanism.
The request
–> GET https://cloud.squidex.io/api/content/
authorization: bearer
<-- 200 https://cloud.squidex.io/api/content
content-type: application/json; charset=utf-8
etag: W/64E275C1C96AE81C278A7A268A11C43BD787C4B65B0D3B33111EB23A3E509E8D
The repeating request
–> GET https://cloud.squidex.io/api/content/
authorization: bearer
if-none-match: W/64E275C1C96AE81C278A7A268A11C43BD787C4B65B0D3B33111EB23A3E509E8D
<-- 200 https://cloud.squidex.io/api/content
I’m receiving 200 instead of 304.
Is that something Squidex doesn’t support or the configs on my side are incorrect.
Thanks for the help!
Are you sure that you have not changed anything in between?
Hi, Sebastian.
Yes. I’m sure. The content on the server is untouched.
What is more, the repeating request’s response has the same Etag i’m sending in the request
It is actually a bug. Will be fixed soon. The order in which things are calculated is wrong: First the comparison of the etags and then the etag calculation.
Thanks for a quick turn around on that. I will be waiting for the fix. Please, let me know when it’s done.
Best regards,
Vitaliy.
1 Like
Thanks @Sebastian . Works as expected!
1 Like
Aesome, thanks a lot for the feedback.
1 Like
system
Closed
October 19, 2022, 3:34pm
11
This topic was automatically closed after 2 days. New replies are no longer allowed.