You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 30, 2024. It is now read-only.
When using express-cors with the
ETag
header included in corsoptions.headers
, theETag
header is still missing.Here's my relevant setup code:
My api route:
Plus my client request:
Here are the raw response headers received from my API, when called from DHC (REST client):
but when making that same request using request in my SPA app, I only get this header:
As seen in request/request#1890 (comment), this can be resolved by the following:
Can we add the appropriate means to use
Access-Control-Expose-Headers
toexpress-cors
The text was updated successfully, but these errors were encountered: