@Pherserk can you try CONTENT_TYPE or HTTP_CONTENT_TYPE... FYI you're passing in server parameters, not headers. Maybe

However at first sight your version should work too based on

Can you debug where stuff gets lost?

@ro0NL

Just added a failing test on this fork at line 167
https://github.com/Pherserk/browser-kit/blob/master/Tests/ClientTest.php

But due to the nature of the mock TestClient, I think it is not reliable.

@ro0NL
Probably I'm messing up things, some headers passed in the ServerBag are translated to headers.
I should use the headers bag, so what should be the correct way to call the client method I'm using to send the request?

Just to be more precise, I'm developing a Json Api user management util.

I use to validate Json Api request with this validator:
https://github.com/Pherserk/symfony2_demo_article_feed/blob/e409b71541f36decc0e1d804b6fa3a49bcb31498/src/AppBundle/Service/JsonApi/Validator/JsonRequestValidator.php

And I'm testing controllers using this util:
https://github.com/Pherserk/symfony2_demo_article_feed/blob/e409b71541f36decc0e1d804b6fa3a49bcb31498/src/AppBundle/Test/ApiWebTestCase.php

This is an example usage of this test util at line 37
https://github.com/Pherserk/symfony2_demo_article_feed/blob/0f07fa57f51dbb16cf63d374999b570e5c693ad6/src/AppBundle/Tests/Controller/Api/UserGroupControllerTest.php

Many, many thanks.

From your issue i kinda assumed you were using WebTestCase::createClient So perphaps compare to what Symfony\Component\HttpKernel\Client does, ie filtering the request correctly, here's where the magic happens.

Next your TestClient::doRequest is foobar.. it doesnt use $request at all.. so yes it's not reliable.

Im lost.. what exactly is the issue? WebTestCase, TestClient?

@ro0NL
Looking at the Client class in Browserkit component:

$this->internalRequest = new Request($uri, $method, $parameters, $files, $this->cookieJar->allValues($uri), $server, $content);

$this->request = $this->filterRequest($this->internalRequest);

if I dump the internalRequest, it preserves the content-type header, while request, does override it with the "application/x--www-form-urlencoded" value.
But I can't understand how this happens.

This is guessing.. i can have a look tonight maybe. But by default the request is not filtered.. ie $this->internalRequest === $this->request. So something else's happening down the chain.. cant you search for application/x--www-form-urlencoded and go from there?

@xabbuh i think we can close this issue,
I have opened this pull request, that is related to this, that is not a bug, but a sometimes difficult to spot behaviour.

symfony/http-foundation#32

@xabbuh @javiereguiluz @ro0NL
according to this line https://github.com/symfony/http-foundation/blob/master/Request.php#L369
If you set
$client->setServerParameter('CONTENT_TYPE' ,'ANY OTHER FORMAT');
OR

$client->request(
            'POST',
            'URL',
            [],
            [],
            ['CONTENT_TYPE' => 'ANY OTHER FORMAT'],
            ''
        );

this should works

Closing because this should work as explained by @petertanath. @ro0NL thanks for your help here too.

Can confirm that this works as expected:

$client->request(
    'POST',
    '/api/devices',
    [],
    [],
    [
        'CONTENT_TYPE' => 'application/ld+json',
    ],
    json_encode([
        'country'    => $country['@id'],
        'deviceId'   => 'randomDeviceId',
        'deviceType' => 'IOS',
    ])
);

Maybe this will help us symfony/browser-kit#10