Closed molnarg closed 11 years ago
I fixed this issue in master repo. Please pull the latest changes and if it works, please close this issue.
Thanks, it seems to work! Btw, what was the problem?
The problem is that whenever backend connection got eof from backend server, frontend spdy connection issues rst_stream. It is valid for http1.1 to indicate the end of response body by eof. The fix is if response seems complete, don't issue rst_stream.
The weird 64k size is caused by flow control as you guessed.
Thx for the explanation :)
I've been toying with shrpx, and I think it's great, but I've run into an issue. I have backend server with a fast HTTP connection to shrpx, and it always sends chunked data. The connection on the frontend (which is SPDY) is much slower.
The client successfully connects to the server, starts downloading data, but it halts after a while (with stream reset). Here's what I see in verbose mode:
The log on the server:
The successfully downloaded data is exactly 65536 bytes which is strange. I think it has to something with buffering... If I change window size on the client, the downloaded size changes, but never reaches the full file size, which is 89460 (even when it is set to 30).
When the backend link is slower, say I change the delay from 10ms to 50ms (it is simulated on localhost) then the problem goes away. When my backend server sends the whole content in one big chunk, the problem goes away again.
I do have a pcap trace as well, I uploaded it here: https://docs.google.com/file/d/0Bzj2UbMqUIfrRGdXZVZLRjFUdmc/edit?usp=sharing