-
Notifications
You must be signed in to change notification settings - Fork 45
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
Api v2 management allows swagger config to have basepath and path both set to / #253
Comments
If an API happens to be created with a basepath and path of |
FWiW, I would like this to work. I can't remember the last time I created an API that didn't have a root endpoint. |
@akrabat but would you really want an API that has a root endpoint and basically no base path? |
To be honest I have no idea what the base path is and how it differs from the api path. I do want to be able to do |
I can see how a URL like "https://my-cnamed-domain.com/" |
Yes. For APIs, I was thinking along the lines of the Home Documents for HTTP APIs proposal. |
When it comes to the typical REST API, I don't know how often this scenario occurs. The HTML use case is the most compelling, given that you typically want a home document. Obviously, this is a use case for Whisk itself, but is it one for the API gateway? Would someone typically front an HTML page with the gateway? |
When creating a new api, a swagger is sent to api management with both base path and operation path set to
/
the API doesn't error out.To reproduce you should could use the WSK CLI
api management doesn't return error to know that there is an invalid combination to have both base path and operation path set to
/
The text was updated successfully, but these errors were encountered: