-
-
Notifications
You must be signed in to change notification settings - Fork 529
Failed load UI behind reverse proxy (Failed to load API definition) #736
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
Comments
There is no known issues on reverse project. You can have a look at the necessary configuration if you are using a reverse proxy in this section: And this is the link to a sample code using spring-cloud-gateway in microservices architecture: |
I had written an example of the project with the failure. https://github.com/krummerd/openapi-issue/tree/master/openapi-gateway |
The current springdoc version is 1.41 I also encountered the same problem. Steps to reproduce: If it is accessed through the gateway for the first time, the initial urls object is If you access it through Conversely, if you access During the investigation, it was found that the |
Upgrade to 1.4.2-SNAPSHOT problem solved But there is another problem 1.4.1 version file After some searching, addGroup was moved to the |
There're two microservices: Api Gateway (http://localhost:8080/) & User (http://localhost:8082/).
If you make a first request to swagger for User through Api Gateway: http://localhost:8080/user/ the config will be generated, but when you try to get User config from direct request to http://localhost:8082/ we can see Fail.
And also it's doesn't work vice versa:
if your first is a direct request without Api Gateway: http://localhost:8082/ then User config will be generated, but when you try to get User config through Api Gateway(http://localhost:8080/user/).
I think this can be fixed, for example, for each request we can generate configs, without caching.
But springdoc.cache.disabled doesn't help.
The text was updated successfully, but these errors were encountered: