You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't strictly a gRPC-web bug, but it's an incompatibility between the gRPC-web binary protocol and the developer tooling Google Chrome provides, so hopefully y'all can communicate internally 馃檪 I don't have a lot of faith that my in-browser feedback will go anywhere.
The payload is supposed to be passed via the --data-raw flag, however bash doesn't support \0 bytes in strings and so this ends up as an empty string. Demo:
This isn't strictly a gRPC-web bug, but it's an incompatibility between the gRPC-web binary protocol and the developer tooling Google Chrome provides, so hopefully y'all can communicate internally 馃檪 I don't have a lot of faith that my in-browser feedback will go anywhere.
Chrome's dev tools includes a very useful "Copy as cURL" tool to generate a
curl
command to reproduce a given request. However I've observed that the generated command is malformed for (some?) gRPC-web requests due to\0
bytes in the request body which bash and other shells, as well as Unix command lines, are incompatible with.Here's a sanitized example command generated by Chrome:
The payload is supposed to be passed via the
--data-raw
flag, however bash doesn't support\0
bytes in strings and so this ends up as an empty string. Demo:This causes the request to fail - including
-v
in thecurl
command shows the following response headers:I believe the only way to send
\0
bytes viacurl
is reading from a file / stdin, something like:The text was updated successfully, but these errors were encountered: