Content-Type is set to application/json when it should be application/x-www-form-urlencoded
Reported by Matt Todd | 2008-08-28 17:06:00 UTC | in Release 0.5.3
This needs to be changed.
However, it may be interesting to support application/json as an alternative, a configuration option for instance. Since the application/json Content-Type isn't handled by default in Rack, perhaps a middleware should be written to support this.
Comments and changes to this ticket
-
Matt Todd 2008-08-28 17:16:39 UTC
- State changed from “new” to “resolved”
(from [8847928b1b28cc3a9191920df328d4fac52a1202]) Fixed issue with the Content-Type being set incorrectly. Fixes specs failing. [#60 state:resolved] http://github.com/mtodd/halcyon/...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
People watching this ticket
Matt Todd
Referenced by
-
61
Conditionally send body content as application/json
Refer to #60 for the original idea.
-
60
Content-Type is set to application/json when it should be application/x-www-form-urlencoded
(from [8847928b1b28cc3a9191920df328d4fac52a1202]) Fixed i...
-
62
Client should set Accept header
For consistency (and to indicate in the future when XML i...