Keep original headers, so the PUT/POST operations aren't bloked

[xrogers]

Without this, some headers could be dropped and POST/PUT operations will not work anymore.

[vinceAmstoutz]

Thanks for your contribution, @xrogers! However, your code addresses a custom need and should not be included in the documentation.

[xrogers]

@vinceAmstoutz This is not correct. The provided example breaks in the current version POST actions. Try it out. It's not related to any specific use case, just basic functionality.

[J3m5]

Hello @xrogers, could you provide a reproduction, please?

In its current state, I can't see how adding a default parameter can change the return value of the getHeaders function.

The options object with the headers property, which is passed to the parseHydraDocumentation function, has this signature.

As you can see, it doesn't specify any parameter, and nothing is passed to it when it is called.

[xrogers]

HI @J3m5
I'm quite swamped to prepare the example, but the issue relates to code from this change: api-platform/admin@66dca9c#diff-a3ad30593f2f6c73e4e5b94fbdec633ffec199309aa092ebdf98ad4ed10a95bcR501 for example
As you can see, content type header is modified in case of PATCH.
With the code from docs this header would be over-ridden/cleared.

[xrogers]

Also see my last commit, somehow it is not visible in this PR: xrogers@30a9782