Skip to content

Refactor: Improve Handling of Allowed Origins and Methods in CorsFilter #132

Description

@VonAdamo

Refactoring Issue

The code snippet below needs refactoring for cleaner and more maintainable handling of allowed origins and HTTP methods:

Code with hardcoded ALLOWED_ORIGINS and ALLOWED_METHODS

Problem

  • ALLOWED_ORIGINS and ALLOWED_METHODS are currently hardcoded as static fields.
  • This approach limits flexibility and makes configuration changes harder.

Suggested Improvements

  • Move these values to application.properties
  • Make the handling of allowed origins and methods more dynamic to support future changes.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions