Calling all options even if origin header is not present. Fix #18 - Not setting headers on Koa2 / Node 6.2 #87
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.
Calling all options even if origin header is not present. Fix #18 - Not setting headers on Koa2 / Node 6.2
As Origin header is not set in all fetch. I understand that we need to be able to validade, even if the origin is not present. We are still following https://fetch.spec.whatwg.org/#http-origin but grating headers to be added to response on user needs(Options functions to be called).
I even checked on https://expressjs.com/en/resources/middleware/cors.html and I noticed, so far, that the handlers are called even though the request has no origin, Follow the request:
https://www.rfc-editor.org/rfc/rfc6454#section-7.3
Fixes #18
Checklist