Sorry about that... Pocket email.
--
Richard Schneeman
http://heroku.com
@schneems
Sent from the road
On Wednesday, October 31, 2012 at 10:15 AM, Richard Schneeman wrote:
> S w mill wxswcsswxe ce cxssxsqseaxqxxqs six desqssx. W ce cedsdc cx
> dA
>
> --
> Richard Schneeman
> http:
S w mill wxswcsswxe ce cxssxsqseaxqxxqs six desqssx. W ce cedsdc cx dA
--
Richard Schneeman
http://heroku.com
@schneems
Sent from the road
On Wednesday, October 31, 2012 at 6:37 AM, Christopher COCCHI-PERRIER wrote:
> Hi,
>
> Currently I see many applications using custom accept hea
A. S
--
Richard Schneeman
http://heroku.com
@schneems
Sent from the road
On Wednesday, October 31, 2012 at 6:37 AM, Christopher COCCHI-PERRIER wrote:
> Hi,
>
> Currently I see many applications using custom accept headers for their API
> versionning such as application/vnd.foo-v1+json or a
> Shouldn't Rails coerce these new almost standart headers to application/json
> and applicatioin/xml (for previous example) ?
No, because 'application/vnd.foo-v1+json' is not 'application/json.'
The "+foo" convention was actually introduced in RFC3023, specifically
for XML formats. But it's only
Hi,
Currently I see many applications using custom accept headers for their API
versionning such as application/vnd.foo-v1+json or
application/vnd.bar-3+xml. But when Rails receive such an accept header, it
cannot convert it to a standart Mime::Type and thus causing problems errors
when using
