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
Describe the bug
When using the "bearer" auth method, the "vendure-auth-token" cannot be read from another origin since it is a non-standard header.
If you want clients to be able to access other headers, you have to use the Access-Control-Expose-Headers header. The value of this header is a comma-delimited list of response headers you want to expose to the client.
As it stands the server would have to be manually configured to allow the vendure token header to be read from another origin:
Expected behavior
This should not be something the developer needs to think about. It should be enabled by default if the "bearer" method is being used.
Care needs to be taken to not override any existing CORS options specified in the config.
Environment (please complete the following information):
@vendure/core version: 0.1.2-beta.11
The text was updated successfully, but these errors were encountered:
Describe the bug
When using the "bearer" auth method, the "vendure-auth-token" cannot be read from another origin since it is a non-standard header.
As it stands the server would have to be manually configured to allow the vendure token header to be read from another origin:
Expected behavior
This should not be something the developer needs to think about. It should be enabled by default if the "bearer" method is being used.
Care needs to be taken to not override any existing CORS options specified in the config.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: