vainquit's profile - activity

"TCP Previous Segment not captured" occurs and the client stop reading the last few bytes from inputstream under high c

"TCP Previous Segment not captured" occurs and the client stop reading the last few bytes from inputstream under high c

"TCP Previous Segment not captured" occurs and the client stop reading the last few bytes from inputstream under high c

That's really a good way to determine which side cause the issue! I have compared the SHA-1 values between the original

"TCP Previous Segment not captured" occurs and the client stop reading the last few bytes from inputstream under high c

"TCP Previous Segment not captured" occurs and the client stop reading the last few bytes from inputstream under high c

"TCP Previous Segment not captured" occurs and the client stop reading the last few bytes from inputstream under high c

That's really a good way to determine which side cause the issue! I have compared the SHA-1 values between the original

Sorry, my fault~~ I have re-uploaded the loopback package....And yes, the client is losing data, not only at the downloa

Sorry, my fault~~ I have re-uploaded the loopback package....And yes, the client is losing data, not only at the downloa

Sorry, my fault~~ I have re-uploaded the loopback package....

"TCP Previous Segment not captured" occurs and the client stop reading the last few bytes from inputstream under high c

Hi, I guess it's not the proxy's case. I have disabled the proxy, and also tried to run the server and app both on a loc

"TCP Previous Segment not captured" occurs and the client stop reading the last few bytes from inputstream under high c

The cilent (emulator of android studio) makes a post request to a remote server (port:80, built by Flask in centos7). The connection was built successfully, and the server began to transmit a lot of packets to the cilent.

At first, everything seemed to go well: the cilent has received many normal packets and read infomation from them. But suddently, the server sent a packet flagged with [RST,ACK], and the cilent got an erro "java.net.SocketException: Connection reset".

(screenshot: https://imgur.com/6l7PQ8Z) (download the pcapng: https://easyupload.io/vophjy, password:wireshark) (Packets were captured on client side. I also captured both on server side and client side at the meantime, and uploaded them in the "update" section below)

My code in Android Studio (worte with JAVA) is like this:

        ..........
        InputStream in=connection.getInputStream(); //connection is a HttpURLConnection
        StringBuilder strbd =new StringBuilder(); 
        byte[] bbuf=new byte[1024];
            while(in.read(bbuf)>0){
                strbd.append(new String(bbuf,0,in.read(bbuf)).trim());
            }
        } catch (IOException e) {
            e.printStackTrace();
            Log.d("ppppx", String.valueOf(strbd.length()));//output:7784, or 9187, or 10079, etc...
        }
        ............

I have tried everything I can to find the reason, but failed, due to my limited knowledge in TCP/IP protocol. I will be really grateful if you can give me an enlightenment, thanks!

----------------------------------------------------------update---------------------------------------------------------------

I just captured the packets both on the client side and the server side at the meantime. I do this work twice, and upload all of them ( view the images and download the packets on http://118.89.144.241/)

Great explanation!Now I know why the loadbalancer has the potential to terminate the connection. As for all the packet

Sure!I have uploaded the normal packets of both side on http://118.89.144.241/. Some RST packets are still captured, but

After transmitting many normal packets in response to a post request,the server suddently sent [rst,ack] The cilent (emu

By the way, is it a common phenomenon that sending HTTP post with "Transfer-Encoding: chunked" in header will result in

OH!!!That's great!!That's great!It works!!You are right!!Everything runs perfectly,as soon as I delete "setChunkedStream

Thank you for you reply :) At least I can locate the problem on the server side now. I would send a ticket to the custom

@bubbasnmp emmm....the original answer didn't include the log of the server side. And I just re-captured them on both se

@SYN-bit Hi, I made the capture on the client side. My wireshark captured all the packets under the "wifi" option ( whic

After transmitting many normal packets in response to a post request,the server suddently sent [rst,ack] The cilent (emu

After transmitting many normal packets in response to a post request,the server suddently sent [rst,ack] The cilent (emu

After transmitting many normal packets in response to a post request,the server suddently sent [rst,ack] The cilent (emu

After transmitting many normal packets in response to a post request,the server suddently sent [rst,ack] The cilent (emu