fix: /api returns JSON 404 instead of HTML for unmatched routes - #96
Merged
Conversation
The /api directory previously had a page.tsx that rendered an HTML API documentation page at the /api URL. This caused API consumers making requests to undefined endpoints to receive 28KB of HTML instead of a proper JSON error response. Changes: - Moved API docs from /api to /api-docs - Created catch-all route at /api/[[...slug]] returning JSON 404 - All previously working API routes remain unchanged
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
2 participants
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.
Description
Previously, GET /api served an HTML documentation page. API consumers calling undefined endpoints received 28KB of HTML instead of a proper JSON error, breaking client error handling.
Changes
Related
Addresses the MEDIUM issue reported in #90
Testing