Skip to content
This repository has been archived by the owner on Sep 14, 2022. It is now read-only.

Is application/x-www-form-urlencoded content type supported? #45

Closed
mangvlad opened this issue Mar 21, 2013 · 2 comments
Closed

Is application/x-www-form-urlencoded content type supported? #45

mangvlad opened this issue Mar 21, 2013 · 2 comments

Comments

@mangvlad
Copy link

I have a PUT call that needs to have Content-Type header set to "application/x-www-form-urlencoded" and also to include 5 parameters in the POST body:

username
password
scope
grant_type
client_id

It also has different Error responses with different JSON objects returned.

What would be a proper/working way to describe this?

(So far I am unable to find any way for how to send proper Content-Type and there is no place to describe that the body should include 5 separate parameters. There is also no place to specify that Errors will include JSON of a particular format/type)

Thanks.

@fehguy
Copy link
Contributor

fehguy commented Mar 25, 2013

Hi, you are looking for this:

https://github.com/wordnik/swagger-core/wiki/Specification-Roadmap

item 2.0. Working on getting that first into the UI, then into each of the servers. You can follow this issue for that support:

swagger-api/swagger-core#77

@fehguy
Copy link
Contributor

fehguy commented Dec 12, 2013

This is supported now for forms: #84

@fehguy fehguy closed this as completed Dec 12, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants