Unparseable or unreachable OpenAPI definition blocks Swagger UI operation rendering
We deploy Swagger UI as static files behind a reverse proxy that serves the application from a subdirectory. The UI loads, but instead of listing operations it displays a fetch or parse failure for the API definition. Relative spec paths resolve against the page URL, so a subdirectory deployment can request the wrong document, and a malformed or partially co
swagger