Received: (qmail 43224 invoked by uid 501); 19 Feb 2001 18:20:36 -0000 Message-Id: <20010219182036.43212.qmail@apache.org> Date: 19 Feb 2001 18:20:36 -0000 From: Ulf Wolfgramm Reply-To: ulf.wolfgramm@lhsystems.com To: submit@bugz.apache.org Subject: Proxy doesn't deliver all tcp/ip packets to client X-Send-Pr-Version: 3.110 >Number: 7276 >Category: mod_proxy >Synopsis: Proxy doesn't deliver all tcp/ip packets to client >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon Feb 19 10:30:03 PST 2001 >Closed-Date: >Last-Modified: >Originator: ulf.wolfgramm@lhsystems.com >Release: 1.3.4 >Organization: apache >Environment: Linux pc141 2.2.18 #6 Tue Jan 23 16:06:50 CET 2001 i486 unknown >Description: I encountered the problem that my client doesn't get all data that is sent to him by a server from the proxy. At the end of my message I include a slightly edited logfile generated by a tcp/ip sniffer: As we can see, the POST request is successfully delivered from the client to the proxy and from there to the server. The proxy machine gets a positive answer back from the server and even acknowledges it (at 01:01:51.7). But the proxy doesn't deliver this to the client machine. Instead it closes the connection to the client after 5 minutes (at 01:06:53.2). In Apache's access log file I see something like this: POST http://194.174.193.20:9001/webforms 200 0 which says - as far as I know - "no data received from the remote side". The same problem exists with Apache 1.3.17. =================== client <-> proxy =============================== 01:01:48.5 client.1042 > proxy.www: P 1:120(119) ack 1 win 8760 (DF) E...t.@......... .......P...j..JB P."8....POST htt p://194.174.193. 20:9001/webforms HTTP/1.1..Host: 194.174.193.20: 9001..Content-le ngth: 8..Pragma: -1....GDayJu.. 01:01:48.5 proxy.www > client.1042: . ack 120 win 32120 (DF) E..(..@.@....... .....P....JB.... P..x.... 01:06:53.2 proxy.www > client.1042: F 1:1(0) ack 120 win 32120 (DF) E..(..@.@....... .....P....JB.... P..x.... ================================================================= =================== proxy <-> server TCP/IP traffic ================ 01:01:48.8 proxy.1050 > server.9001: P 1:94(93) ack 1 win 32120 (DF) E.....@.@....... ......#)... .... P..x.J..POST /we bforms HTTP/1.0. .Host: 194.174.1 93.20:9001..Cont ent-length: 8..P ragma: -1....GDa yJu.. 01:01:49.1 server.9001 > proxy.1050: . ack 94 win 8667 (DF) E..(b.@.n.l..... ....#).......... P.!./... 01:01:51.7 server.9001 > proxy.1050: P 1:58(57) ack 94 win 8667 (DF) E..ac.@.n.k..... ....#).......... P.!.T...HTTP/1.1 200 OK..Content -length: 8..Prag ma: 0....Matf..H . 01:01:51.7 proxy.1050 > server.9001: . ack 58 win 32063 (DF) E..(..@.@....... ......#)........ P..?.B.. ================================================================= >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]