-
Notifications
You must be signed in to change notification settings - Fork 9
Body types other than JSON are improperly handled when invoking a function #185
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
Comments
Thanks for pointing that out, will have a look |
@encima can you provide a test case where the current setup breaks? preferably a test case with code example. |
sure, will provide an example on Monday! any function that takes a string will break as it will be encoded as JSON |
aaand it seems there was already a fix for it! but, to stay a person of my word:
Using this (before the fix) would set the |
@encima yeah a fix was made by @juancarlospaco on the day you reported it. We will get the fix merged in and get a new release out soon. Also thanks for providing the example above. |
When invoking a function, the content type is detected and set as a header but the
httpx
call sets thejson
property but, for strings, this would becontent
.The text was updated successfully, but these errors were encountered: