Error "^ "A valid request line was not found in the provided string""

[tshafer]

After upgrading to 3.0 i am getting the message ^ "A valid request line was not found in the provided string" after a few requests come in. I cant seem to figure out why, anybody else getting this?

[mpociot]

Are you able to reproduce this with a specific request?

[tshafer]

i am still debugging but so far it is only happening on post requests, options and get seem to work fine.

[mpociot]

Does the request itself work fine though and it's just that you see this output? Or is the request ignored?

[tshafer]

Its very random, sometimes works on post, sometimes it fails. Are you throwing A valid request line was not found in the provided string on your end and not in the package?

I am returning a response for every request I get in, either a 404 or a 200.

Side note, it usually takes me 3 to 4 times to start the server, I get this error a few times before it works.

  Expose\Client\ProxyManager::createProxy(): Argument #1 ($clientId) must be of type string, null given, called in
  phar:///Users/tomshafer/.composer/vendor/beyondcode/expose/builds/expose/app/Connections/ControlConnection.php on
   line 52

[tshafer]

Sorry, the request succeeds, and then I get the problem.

[daugaard47]

I'm having the exact same issue having Stripe send me an invoice.payment_succeeded event. It goes through and I get the payload, but and then I get that "valid request line" message and expose crashes.
On stripes side it says the event failed even though I received the payload.

The stripe response is HTTP status code 404 (Not Found) I think expose needs to add a longer timeout or it cannot handle the size of the requested payload. I would post the payload, but it's too long. @mpociot If you need to see the payload let me know and I'll drop it in here.

Please post in here when a patch has been released.
Thank you.

[mpociot]

I just tagged version 3.0.1 which fixes this issue.
Version 3.0.1 also adds a Stripe request plugin:

You can update manually by running expose self-update

[tshafer]

Not erroring out anymore. Thanks!