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
Issue:
When Octopus Server is configured with a Virtual Directory (e.g. localhost:8080/octopus) Swagger doesn't incorporate the virtual directory when generating the API calls.
Testing:
Configure a binding for Octopus with a virtual directory, in testing I used localhost:8080/octopus
Browse to Swagger using the virtual directory binding - http://localhost:8080/octopus/swaggerui/index.html
Pick an example - GET /api/users/me
Select Try me out
API call is generated as curl -X GET "http://localhost:8080/api/users/me" -H "accept: application/json" which fails with a 503 Service Unavailable
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.
lockbot
locked as resolved and limited conversation to collaborators
Nov 23, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bugThis issue represents a verified problem we are committed to solving
Issue:
When Octopus Server is configured with a Virtual Directory (e.g.
localhost:8080/octopus
) Swagger doesn't incorporate the virtual directory when generating the API calls.Testing:
localhost:8080/octopus
http://localhost:8080/octopus/swaggerui/index.html
GET /api/users/me
curl -X GET "http://localhost:8080/api/users/me" -H "accept: application/json"
which fails with a503 Service Unavailable
The text was updated successfully, but these errors were encountered: