-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
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
OpenAPI spec wrong URL #161
Comments
Hazmi35
added a commit
to hzmifork/elysia-swagger
that referenced
this issue
Oct 17, 2024
Fixes elysiajs#161. This will also work when you don't specify any prefix to Elysia but uses Traefik Middlewares to strip /api prefix too.
While #162 fixes externally set prefixes from Traefik for example, it does not respect Elysia prefix as stated in |
Hazmi35
added a commit
to hzmifork/elysia-swagger
that referenced
this issue
Nov 21, 2024
Fixes elysiajs#161. This will also work when you don't specify any prefix to Elysia but uses Traefik Middlewares to strip /api prefix too.
Hazmi35
added a commit
to hzmifork/elysia-swagger
that referenced
this issue
Nov 29, 2024
Fixes elysiajs#161. This will also work when you don't specify any prefix to Elysia but uses Traefik Middlewares to strip /api prefix too.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was using Traefik with these match rules.
This will route all
domain.com
with the prefix/api
to the desired service which is our backend running Elysia with swagger. With #16 it was fixed to use the prefix from Elysia configuration, but on the latest version the Swagger option url is in the wrong url. (Does not respect prefix at all).The text was updated successfully, but these errors were encountered: