> 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).
The fact is, after pushing the button I *send* data to the other side. Indeed, Mozilla recognises this fact, while Galeon does not: Mozilla's message is correct, Galeon's is not. This is the code that shows the file name input cell and the upload button: <input class="altButton" name="uploadedfile" type="file"> <input class="altButton" name="upload" value="Upload" type="submit"> > About problem 2, I can't tell who is to blame, the server or the > client I made some tries before sending the report, and I am reasonably sure that it is a timeout problem. > 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. Ok, this is what I had looked for before sending the report and could not find :-) But I had looked under ~/.galeon/mozilla/galeon/prefs.js Where are those values stored? > Let me know about the results of your findings. Well, it turns out that changing the timeout has no effect :-( Okay,resorting to tcpdump... Hey! You were right in suspecting, it's the servar which times out! After 30 seconds it resets the connection, and sends not 1 but 43 TCP reset packets... All right, thanks for your time, and this bug report restricts to a bad message and could be downgraded to minor. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
