Updating koa/cors to 3.4.2 in order to fix cors filter origin problem #14357 #14552
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.
Updating koa/cors to 3.4.2 in order to fix cors filter origin problem #14357
There was a bug that is fixed on koa/cors 3.4.2 version.
Fixes #14357
What does it do?
In order to fix #14357 I had to fix another bug on koa/cors, as my PR was merged -> koajs/cors#87 I'm creating this PR in order to update the lib
Why is it needed?
Koa/cors was not calling origin middleware when the origin header was not present. Hence, even when you set credentials as false, the middleware was not called and people could not get Access-Control-Allow-Origin as '*'.
How to test it?
Set credentials as false on config/middlewares.js, call any API in order to retrive Access-Control-Allow-Origin as '*' as DEFAULT.
Related issue(s)/PR(s)
Fix #14357
Please, could you add https://hacktoberfest.com/ label?