We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We should load swagger from relative url because nest application could be proxied with some path prefix by some server like NGINX behind.
For example, we have Nest app with simple /docs/ route. And some SPA application on same domain. We will configure NGINX like
location /api { // upstream to Nest app } location { // route everything didnt match /api prefix to static files }
In these cause a broken link swagger.json because it will be generated from the root
And these why all static files are loaded in original SwaggerModule
SwaggerModule
<script src="./swagger-ui-bundle.js"> </script> <script src="./swagger-ui-standalone-preset.js"> </script> <script src="./swagger-ui-init.js"> </script>
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
We should load swagger from relative url because nest application could be proxied with some path prefix by some server like NGINX behind.
For example, we have Nest app with simple /docs/ route. And some SPA application on same domain. We will configure NGINX like
In these cause a broken link swagger.json because it will be generated from the root
And these why all static files are loaded in original
SwaggerModule
The text was updated successfully, but these errors were encountered: