@hlship do you think something like this would be doable with Lacinia? https://github.com/graphql/graphql-js/issues/407

It's already there.

In summary, modifying the context (passed to resolvers) during resolution (in a resolver)

for all the subtree

oh really?!

I must have missed it in the doc; could you tell me the API please?

http://lacinia.readthedocs.io/en/latest/resolve/context.html

Ah, silly me. Thanks, that’s great

@malcolmsparks @hlship thanks for input, I wrote my comment back there. I suggest we’re supporting more clients even with invalid headers

it’s easier to fix it there than from all of the clients

Yes, Postel's Law applies here. Though iirc the Content-Type is strictly invalid if there are invalid parameters. And standards are important. But in this case it seems better to ignore the parameter. However, this is a bug in the client that should be communicated. The internet is only the internet when standards are upheld. :)

I'm thinking that we could introduce a Pedestal interceptor that touches up the content-type for this case, to make it obvious that this is temporary.