Skip to content

process the CORS options only once (as opposed to every time the CORS middleware is applied to a handler) #263

New issue

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

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

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jub0bs
Copy link

@jub0bs jub0bs commented Apr 26, 2025

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update
  • Go Version Update
  • Dependency Update

Description

The CORS middleware resulting from handlers.CORS would unnecessarily re-process the CORS options every time it would be applied to a handler.

With this change, the CORS options are processed only once, when the middleware is created.

Added/updated tests?

  • Yes
  • No, and this is why: this is only refactoring for better performance. The external behavior hasn't changed.
  • I need help with writing tests

Run verifications and test

  • make verify is passing
  • make test is passing

@jub0bs jub0bs changed the title process the CORS options once process the CORS options only once (as opposed to every time the CORS middleware is applied to a handler) Apr 26, 2025
@jub0bs
Copy link
Author

jub0bs commented Apr 26, 2025

Tip for reviewing this PR more easily: hide whitespace changes.

The CORS middleware resulting from handlers.CORS would unnecessarily
re-process the CORS options every time it would be applied to a handler.

With this change, the CORS options are processed only once, when the
middleware is created.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant