Skip to content
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

Swagger examples don't include Virtual Directories #4291

Closed
alexrolleyoctopus opened this issue Feb 16, 2018 · 3 comments
Closed

Swagger examples don't include Virtual Directories #4291

alexrolleyoctopus opened this issue Feb 16, 2018 · 3 comments
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving
Milestone

Comments

@alexrolleyoctopus
Copy link

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:

  1. Configure a binding for Octopus with a virtual directory, in testing I used localhost:8080/octopus
  2. Browse to Swagger using the virtual directory binding - http://localhost:8080/octopus/swaggerui/index.html
  3. Pick an example - GET /api/users/me
  4. Select Try me out
  5. 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
@alexrolleyoctopus alexrolleyoctopus added kind/bug This issue represents a verified problem we are committed to solving area/Integration labels Feb 16, 2018
@MarkSiedle
Copy link

Swagger base path

@octoreleasebot
Copy link

Release Note: Swagger spec now takes virtual directories into account

@lock
Copy link

lock bot commented Nov 23, 2018

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.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

4 participants