[LOCKLITE-144] Disable Swagger in production environment#114
Merged
[LOCKLITE-144] Disable Swagger in production environment#114
Conversation
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR implements security measures to disable Swagger documentation endpoints in production environments to prevent API documentation exposure.
- Adds Next.js middleware to block access to Swagger endpoints in production
- Returns 404 responses for
/api/swaggerand/api/docspaths when NODE_ENV is production - Allows normal request processing for all other routes and non-production environments
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Security tags :
OWASP-A05:2021