Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

feat: support using regular expressions as CORS origin #509

Merged
merged 6 commits into from
Sep 19, 2024

Conversation

P4sca1
Copy link
Contributor

@P4sca1 P4sca1 commented Aug 9, 2024

Types of changes

  • Bug fix (a non-breaking change which fixes an issue)
  • New feature (a non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Description

Changes CORS options type to only allow serializable values. Add a new useRegExp property, that when set to true parses all origin values to a RegExp.

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes (if not applicable, please state why)

Signed-off-by: Pascal Sthamer <10992664+P4sca1@users.noreply.github.com>
Copy link

vercel bot commented Aug 9, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nuxt-security ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 9, 2024 4:42pm

@P4sca1 P4sca1 changed the base branch from main to chore/2.0.0 August 9, 2024 15:52
@P4sca1 P4sca1 mentioned this pull request Aug 9, 2024
6 tasks
P4sca1 added 3 commits August 9, 2024 18:29
Signed-off-by: Pascal Sthamer <10992664+P4sca1@users.noreply.github.com>
Signed-off-by: Pascal Sthamer <10992664+P4sca1@users.noreply.github.com>
Signed-off-by: Pascal Sthamer <10992664+P4sca1@users.noreply.github.com>
Signed-off-by: Pascal Sthamer <10992664+P4sca1@users.noreply.github.com>
@P4sca1 P4sca1 changed the title fix: support using regular expressions as origin fix: support using regular expressions as CORS origin Aug 9, 2024
@P4sca1 P4sca1 changed the title fix: support using regular expressions as CORS origin feat: support using regular expressions as CORS origin Aug 9, 2024
Signed-off-by: Pascal Sthamer <10992664+P4sca1@users.noreply.github.com>
@Baroshem
Copy link
Owner

Looks great to me, @vejja what are your thoughts on that? Could we make it for the 2.0.0 release? Or should we reschedule it to 2.1.0? :)

@P4sca1
Copy link
Contributor Author

P4sca1 commented Sep 2, 2024

@Baroshem Are there any news? Would be great if this could be merged and a new RC release gets drafted.

@Baroshem
Copy link
Owner

Baroshem commented Sep 9, 2024

@vejja looking for your feedback :)

@Baroshem Baroshem requested a review from vejja September 17, 2024 07:31
@Baroshem Baroshem merged commit 85e5c91 into Baroshem:chore/2.0.0 Sep 19, 2024
3 checks passed
@vejja
Copy link
Collaborator

vejja commented Sep 19, 2024

LGTM, sorry for delay

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants