fix(swagger): serve Swagger sob /api/swagger, nao /swagger - #256
Merged
Conversation
Em producao, o BFF/reverse proxy (LayoutParserReact/server) so encaminha /api/* para esta API - qualquer rota fora desse prefixo cai no catch-all do SPA React, que devolve a propria pagina de erro 404 do front em vez do Swagger. Confirmado em producao apos o deploy do PR #254: GET /swagger retornava a tela de erro do front-end, nao o Swagger UI. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DcGnNut7qW3Zz5qEZxXPp6
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Merged
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
1 participant
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.
Problema
Em producao, apos o deploy do PR #254 (Swagger habilitado em todo ambiente), acessar
/swaggerretornava a pagina de erro 404 do SPA front-end, nao o Swagger UI.
Causa: o BFF/reverse proxy (LayoutParserReact/server) so encaminha
/api/*para esta API -qualquer rota fora desse prefixo cai no catch-all do React, que mostra sua propria tela de erro.
Correcao
Move o Swagger para
/api/swagger(UI eswagger.json), dentro do prefixo ja roteado para a API.Teste
dotnet build— 0 erros.https://layoutparser.duckdns.org/api/swaggerno navegador ehttps://layoutparser.duckdns.org/api/swagger/v1/swagger.jsonpara import no Postman.🤖 Gerado com Claude Code