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
I have a Flask app using this Swagger integration behind an internal load balancer in EC2, which I'm accessing in my local browser through SSH port forwarding.
Effectively, this means I enter http://localhost:8070/api/spec.html to access the Swagger endpoint. The problem is that all the resources in that HTML are linking to http://localhost:80 explicitly e.g. http://localhost/api/spec/_/static/swagger-ui.js, which means that they can't be loaded.
Is there any particular reason to avoid relative URLs here?
Thanks
The text was updated successfully, but these errors were encountered:
I have a Flask app using this Swagger integration behind an internal load balancer in EC2, which I'm accessing in my local browser through SSH port forwarding.
Effectively, this means I enter
http://localhost:8070/api/spec.html
to access the Swagger endpoint. The problem is that all the resources in that HTML are linking tohttp://localhost:80
explicitly e.g.http://localhost/api/spec/_/static/swagger-ui.js
, which means that they can't be loaded.Is there any particular reason to avoid relative URLs here?
Thanks
The text was updated successfully, but these errors were encountered: