-
Notifications
You must be signed in to change notification settings - Fork 439
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-string header values on http response throws error #2768
Comments
From @pilot4u on February 22, 2018 11:55 I'm struggling with this issue as well, has anyone managed to overcome this issue? |
@mhoeger - here is the test that might be throwing the same error BadContentType_ThrowsExpectedException_Conneg Right now headers in the proto file are key ,value pairs: RpcHttp Header. Please investigate if we need to move to |
Thanks for finding the related test! I think you're right that we should be able to accept TypedData instead of just string, since V1 lets users do this. The error is that we only accept string:string key value pairs on http headers right now. |
This issue was moved to Azure/azure-functions-language-worker-protobuf#9 |
From @graham-sportsmgmt on February 17, 2018 3:49
azure-functions-core-tools@2.0.1-beta.22
JavaScript HttpTrigger
Local function emulator on Windows 10 x64
I am trying to set a response header in order to flag the length of the result set to our front end code.
This method throws an error:
This method doesn't throw an error, but adds no header to the response:
context.res.setHeader('length', response.length);
Copied from original issue: Azure/azure-functions-core-tools#386
The text was updated successfully, but these errors were encountered: