Unable to Access ETag Header in Fetch API Response

[matti606]

Problem:

Based on the documentation ETag-based caching should be supported. However, I am unable to access the ETag header in the Fetch API response using response.headers.get('ETag'). The ETag header is not visible or accessible through the Headers object.

Details:

• The ETag header is present in the response according to the network tab in the browser's inspector.
• Other headers like Cache-Control and Content-Type are accessible.
• This issue prevents me from utilizing ETag-based caching and cache validation.

[Bertware]

Could you check if this has been fixed? I added additional CORS headers.

[matti606]

Sorry, still can't get the Etag. I see in your commit you describe XHR requests, I'm using fetch or does this not work with fetch?

[Bertware]

XHR/Fetch requests are the same thing. It seems the deploy may have gotten stuck, so you could try again to see if it has been resolved now. Are you perhaps trying to access the liveboard endpoint? I noticed some headers aren't properly populating there.

[matti606]

Hi, thanks for the notice. I have just tested it and it's fixed.

[matti606]

Okay so the headers is only present if there's a 200 response. When checking for a new eTag, the 304 response doesn't have the following headers:

Access-Control-Allow-Headers: *
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: *