File Uploads larger than ~500kb causes Read() error behind nginx about fastcgipp HOT 7 CLOSED

So I can't reproduce this nor find your fork. Any more info?

from fastcgipp.

Apologies - should have put some more info in for replication;

It was a straight build of commit d39ea6d with the echo example doing a file upload with multipart/form-data. (It's been a while.)

I've got it running now on https://mu.uptane.org/ (2017-04-27 23:37 GMT) for the next few hours without the patch. If you upload over 500k, you'll see the server 'disappear' and a custom 502 show up.

Refresh and the page reloads fine, same thread, etc.

stderr shows
Apr 27 19:33:40 uptane.org ./a.out[15963] [warning]: Socket read() error on fd 7: Resource temporarily unavailable

Patch I wrote that was rectifying the issue; https://gist.github.com/samlauzon/1c8b65b6d95ca98f7b7cec21c51a6e85

from fastcgipp.

Hmmm Interesting. I'm just wondering if anyone has seen similar issues. I don't have an nginx server but I can't reproduce with lighttpd or apache. Have you tried it with a separate nginx install?

from fastcgipp.

Ah you know. I think I may have reproduced it.

from fastcgipp.

Alrighty. Can you see if ced61e4 fixes it? After try out the master head and see if it still works (or is fixed) as some other big changes came after.

from fastcgipp.

Sorry about the delay, pulled the latest and built the echo example;
File uploading now outputs:

/a.out[31136] [warning]: Got a non BEGIN_REQUEST record for a request that doesn't exist (x10)
./a.out[31136] [warning]: Socket read() error on fd 7: Resource temporarily unavailable

from fastcgipp.

At last - I was able to make this work; had to ensure buffering was off in nginx.
Thanks!

from fastcgipp.