-
Notifications
You must be signed in to change notification settings - Fork 60
Vendor media types not recognised #87
Comments
ah, that's a very good feature ... will certainly add that next! |
Thanks, looking forward to it. And thanks for a great tool, it's invaluable for testing REST APIs. |
I've noticed another very strange, seemingly related bug:
Does the Content-Type response header of the previous request somehow affect the Content-Type request header of the next one? |
interesting ... I see no reason for that behaviour, none that would be related to the response content type ... can you please open a separate ticket for this (easier to track) I know I keep sounding like a broken record, but new version is coming soon, its a complete rewrite adding many many many new features and allowing for better debugging of issues like these! |
OK, I opened a new ticket. It seemed somehow related to this one, but it could also be completely unrelated. |
Vendor media types (http://tools.ietf.org/html/rfc4288#section-3.2) are the preferred method for REST API versioning according to many sources. However, when a service specifies a vendor media type in the Content-Type header, the Rest Console doesn't recognise it and doesn't parse the response accordingly.
Examples:
The text was updated successfully, but these errors were encountered: