Hi,
On mar, nov 08, 2005, Francesco Potorti` wrote:
> I upload a file on a server using the upload button provided by the web
> site. While uploading the file, the bottom line in the browser says
> "transferring data from site.where.you.want" (while in fact it is
> transferring data to the site).
> After about 30s, a timeout expires and a dialog window appears: "the
> document contains no data" and the upload is interrupted. There is no
> way to upload the data, as the transfer needs more than 30 seconds.
> The same happens with Mozilla. The only difference is that the bottom
> line this time says correctly "sending request to site.where.you.want".
I see two problems in your report:
1/ you don't like the message in the bottom line of the browser
2/ you can't send your data
About problem 1, I don't know how deep you understand the HTTP
protocol, so I'll simply tell you that it might be technically possible
to have two messages, but it might be too much noise for regular usage
of the web. This is because HTTP is a request / response protocol,
each request implies a response, and displaying "I'm sending the
request" and then "I'm receiving the response" might be annoying (it
would flicker on fast sites for example).
About problem 2, I can't tell who is to blame, the server or the
client, from the mere description of the process that you give: did you
succeed in sending so much data from another place / browser to the
same server? to another server? I suppose a network trace would help
diagnosing this, and you can achieve that by using (as root):
tcpdump -n -i eth0 -s 65535 -w my-network-trace.pcap
or simply install and run (as root) the more high-level Ethereal
program (it has a command line alternative, tethereal).
If you think this is a problem on the client (in Mozilla or Galeon),
then you might want to look at the timeouts that one can configure in
mozilla/galeon. You should visit the "about:config" page, and search
"timeout". Here, it shows a "network.http.connect.timeout" parameter
defaulting to 30 seconds, and a "network.http.request.timeout"
parameter which seems to be closer to what you expect.
Let me know about the results of your findings.
Cheers,
--
Loïc Minier <[EMAIL PROTECTED]>
"What do we want? BRAINS! When do we want it? BRAINS!"
