Valery Piashchynski

@revenkroz You actually getting the raw body 😃 (if you use the `raw_body` flag). The body contains all the data you sent to the RR: https://github.com/revenkroz/rr-urlencoded-bug/blob/main/test.php#L11-#L13, it's not just a...

Could you please save the data you receive inside the RR (with and without raw) and attach these files to your repository?

Uh, yeah, I think that's because we're sending the JSON from RR to the PHP worker. We're moving to the PROTO protocol, so we won't have these weird content issues...

@revenkroz Or you can try `multipart` Content-Type 😃

@revenkroz I'll leave this bug open, when I implement RAW proto payloads, I'll ping you here 😃

Hey @Starfox64 👋 I'm working on the fix. Basically, we have to do that because of JSON communication. I'm working on a protobuf-based payloads between the PHP workers and RR...

Hey everyone, we tested this scenario with the new proto encoder, everything works good. You'll need to use `raw_body: true` option to receive untouched by RR payload.

Hey @revenkroz 👋 Did you update PHP worker (composer.json) dependencies?

Cool 👍 The PR is still in progress and will be merged when the PHP deps would be released.

BTW: do not forget to install the `protobuf` dependency via `pecl install protobuf`. This allows PHP to parse protobuf payloads almost 2 times faster.