Issue by kbrandwijk
_Wednesday Sep 27, 2017 at 13:28 GMT_
_Originally opened as https://github.com/graphcool/cli/issues/276_
1 - is fixed and deployed
2 - I assume you are referencing the context.request.headers field. This is supposed to contain headers sent by the user, not the headers specified for a function
@sorenbs What do you mean by headers set by the user? If I have a function set up with headers, and I call that function in the new playground, specifying headers, all of those headers are sent as real headers, and the headers object always stays empty.
For example: https://graphqlbin.com/3lktx
You'll see a header 'myfunctionheader', which I set in Graphcool, shows up as actual header
You don't see the 'myclientheader', specified in the playground, anywhere.
You'll see an empty body.context.request.headers
That's correct. The feature is currently broken :-)
I created a separate feature request for 2): https://github.com/graphcool/graphcool/issues/877 馃檪
Most helpful comment
I created a separate feature request for 2): https://github.com/graphcool/graphcool/issues/877 馃檪