You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not a very high priority I suppose, and I can attempt to fix this with a patch.
In springfox we have this notion of groups. So when we load a url in the swagger-ui if we had something like this http://localhost:8080/api-docs?group=default which returns the following resource listing.
When swagger ui tries to load the api listings, the urls it uses appends the api path to the base url. So the api listing requests end up with urls like this
http://localhost:8080/api-docs?group=default/default/bundle. it should actually be http://localhost:8080/api-docs/default/bundle
The text was updated successfully, but these errors were encountered:
dilipkrish
added a commit
to springfox/springfox
that referenced
this issue
May 7, 2015
using the ?group=<group-name> query parameter. This is to prevent the bug in swagger-ui/ swagger.js
where the api listing is resolved by appending the api url to the url on the swagger page.
more details available @ swagger-api/swagger-ui#1245
related to #727
Not a very high priority I suppose, and I can attempt to fix this with a patch.
In springfox we have this notion of groups. So when we load a url in the swagger-ui if we had something like this
http://localhost:8080/api-docs?group=default
which returns the following resource listing.GET http://localhost:8080/api-docs?group=default
When swagger ui tries to load the api listings, the urls it uses appends the api path to the base url. So the api listing requests end up with urls like this
http://localhost:8080/api-docs?group=default/default/bundle
. it should actually behttp://localhost:8080/api-docs/default/bundle
The text was updated successfully, but these errors were encountered: