We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Example Swagger/OpenAPI definition:
--- openapi: "3.0.1" info: title: "Random Yes/No" version: "1.0.0" servers: - url: "{server}/api" variables: server: default: "https://yesno.wtf" paths: /: get: description: "Yes or no" responses: "200": description: "OK" content: "application/json": schema: properties: answer: type: string forced: type: boolean image: type: string format: uri
The wrong URL used when executing the request from swagger ui when a server url starts with a variable.
I feel this should work as the spec not having any validation issues and there is a similar example in the exaples section on this page https://swagger.io/docs/specification/api-host-and-base-path/ (see SaaS and On-Premise).
Steps to reproduce the behavior:
A request is now performed but it failed due to the request url getting prefixed with https://editor.swagger.io/
https://editor.swagger.io/
A get request to https://yesno.wtf/api/
https://yesno.wtf/api/
When manually replacing the {server} variable in the url with with the default value the hostname is not prefixed and the correct server url is used.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Q&A (please complete the following information)
Content & configuration
Example Swagger/OpenAPI definition:
Describe the bug you're encountering
The wrong URL used when executing the request from swagger ui when a server url starts with a variable.
I feel this should work as the spec not having any validation issues and there is a similar example in the exaples section on this page https://swagger.io/docs/specification/api-host-and-base-path/ (see SaaS and On-Premise).
To reproduce...
Steps to reproduce the behavior:
A request is now performed but it failed due to the request url getting prefixed with
https://editor.swagger.io/
Expected behavior
A get request to
https://yesno.wtf/api/
When manually replacing the {server} variable in the url with with the default value the hostname is not prefixed and the correct server url is used.
The text was updated successfully, but these errors were encountered: