Custom MIME type and versioning cause failures

[araines]

FOSRestBundle 2.0 Beta 2
Symfony 2.7

I'm trying to implement a custom MIME type on my API, and require all clients to use it. This part appears to work fine until I start to try to add versioning.

config.yml

fos_rest:
    view:
        view_response_listener: force
        mime_types:
            json: ['application/vnd.foo.api+json;version=3']
    versioning:
        enabled: true
        resolvers:
            media_type:
                enabled: true
                regex: '/version=(?P<version>[0-9]+)/'
    format_listener:
        enabled: true
        rules:
            -
                path: '^/bracket/'
                priorities: ['json']
                fallback_format: ~
                prefer_extension: false

When I send a request, I get a HTTP406 (Not Acceptable) response:

curl -H 'Accept: application/vnd.foo.api+json;version=3' http://localhost:8080/bar/20

Individually, both of these features appear to work. For example, if I change my mime type as follows:

        mime_types:
            json: ['application/json;version=3']

And send a request:

curl -H 'Accept: application/json;version=3' http://localhost:8080/bar/20

Then I get the response I expect.

Also if I set it to my custom vendor descriptor:

        mime_types:
            json: ['application/vnd.foo.api+json;version=3']

curl -H 'Accept: application/vnd.foo.api+json' http://localhost:8080/bar/20

This also works (I get a HTTP200 response).

[GuilhemN]

Hum there are apparently 2 bugs in cause.
The first one is in FOSRestBundle and is fixed by #1400 but the second one is caused by the symfony Request which removes all the parameters from the mime types (see here).

So until a fix is applied on symfony you have to use this in your config:

mime_types:
    json: ['application/vnd.foo.api+json;version=3', 'application/vnd.foo.api+json']

[GuilhemN]

See symfony/symfony#18255

[araines]

@Ener-Getick appreciate the speedy and detailed response :) Hopefully everything will get sorted at both ends soon!

[GuilhemN]

@araines thank you for your report, we need people like you to tell us when a feature breaks and we don't catch it :-)
symfony/symfony#18255 doesn't contain major changes so I think it will be merged quickly.

[GuilhemN]

Fixed in symfony/symfony#18255, you'll be able to use this fix as soon as patch versions are released ;-)