Lingering connections when adapting huge POST REQUEST from ecap
Hi,
I get a POST request as below. As you can see that the content length is huge for this POST request. In our ecap adapter as soon we see this request we adapt this request and send back a payload response to the client. In most cases this works fine but now and then some request connections would stay in CLOSE_WAIT state with recv queue as huge as 700,00 bytes which we now understand corresponds to the content length in the POST request for example in this case.
I wanted to check with you that do you think that we could be doing something wrong in our POST request adaptation that could be causing squid to go in this state. or would you know based on your experience with squid code base that how could we avoid this or is this a bug?
POST https:/
Connection: keep-alive
Content-Length: 632784
Authorization: SAPISIDHASH 798a27becf38ae9
Origin: https:/
X-Goog-AuthUser: 0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/
Content-Type: application/
Accept: */*
X-Client-Data: CJW2yQEIpbbJAQj
Referer: https:/
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9
Cookie: *******
Host: play.google.com
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- eCAP Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Can you help with this problem?
Provide an answer of your own, or ask Jatin for more information if necessary.