Article delegate-en/4173 of [1-5169] on the server localhost:119
  upper oldest olders older1 this newer1 newers latest
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
Newsgroups: mail-lists.delegate-en

[DeleGate-En] Re: HTTP response size of 1969 bytes fails to be received
06 Oct 2008 10:01:04 GMT (Yutaka Sato)
The DeleGate Project


In message <_A4172@delegate-en.ML_> on 10/06/08(16:04:22)
you Tony Gaspar <> wrote:
 |I upgraded to version 9.8.5 and the bug still occurs. What can I do for
 |you to identify this as a bug? - I can only see it occur when I'm using
 |Telstra NextG Wireless broadband. Over any other network I tested with
 |it's fine. (ie. LAN, Wireless LAN, and Bigpond NextG Wireless broadband)

- tcpdump ... TCP packet sequence
maybe packet capturing is what to do first to see what is happening in
the lower layers.  If there is a something different packet sequence only
in a specific network, it will be a great hint to understand the problem.

- netstat -i ... MTU on the wireless network
the size of MTU and number of errors will be useful to see the quality
of each network.  Tuning the MTU might solve problems.

- TCP_NODELAY in http.c:fflushKeepAlive()
your problem might  be caused by toggling the TCP_NODELAY option in the
function.  If so, simply removing the line including "set_nodelay()" might
solve the problem.

It is usual that a packet is lost on wireless network to cause delay or
freeze.  It depends on configurations including MTU, retransmssion,
compression, encryption or so of each wireless network.

  9 9   Yutaka Sato <>
 ( ~ )  National Institute of Advanced Industrial Science and Technology
_<   >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller

  admin search upper oldest olders older1 this newer1 newers latest
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]