Add missing Origin to the Vary header value when CORS enabled
#534
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR includes the missing
Originheader to the resultingVaryheader value when the CORS feature is enabled according to https://fetch.spec.whatwg.org/#example-vary-origin.Related Issue
It resolves #533
Motivation and Context
How Has This Been Tested?
Before
After
Preflight request
$ curl http://localhost:8788/assets/main.js \ -I -X OPTIONS \ -H "Access-Control-Request-Method: HEAD" \ -H "Access-Control-Request-Headers: content-type" \ -H "Origin: http://localhost:8787" # HTTP/1.1 204 No Content # vary: origin,accept-encoding # accept-ranges: bytes # access-control-allow-headers: origin, content-type, authorization # access-control-expose-headers: content-type, origin # access-control-allow-methods: HEAD, OPTIONS, GET # access-control-allow-origin: http://localhost:8787 # cache-control: public, max-age=31536000 # date: Mon, 24 Mar 2025 03:36:53 GMTWithout CORS:
Screenshots (if appropriate):