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
{{ message }}
This repository has been archived by the owner on Aug 24, 2018. It is now read-only.
That means, you can get api listings by following the paths with the specified format:
http://petstore.swagger.wordnik.com/api/pet.json
Inside the api, you can then access the resource by concatenating the basePath in the api listing with the operation path, which by convention has the .{format} in it, if used.
With this example, the http://localhost:8080/api/pet.json shows the .{format} correctly, but the servlet listens to the the path without the format:
http://localhost:8080/api/pet/3
Note the missing .json in the path
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Swagger defines the request/response format at the api level--it's typically shown in the resource listing like this:
That means, you can get api listings by following the paths with the specified format:
Inside the api, you can then access the resource by concatenating the
basePath
in the api listing with the operation path, which by convention has the .{format} in it, if used.With this example, the
http://localhost:8080/api/pet.json
shows the.{format}
correctly, but the servlet listens to the the path without the format:Note the missing
.json
in the pathThe text was updated successfully, but these errors were encountered: