The http code in libxpnet handles critical http failures by putting the ui into pause mode, and does not communicate to the user what is going on. It really should take a look at the response codes more critically, some of them should be displayed to the user, in some cases the user should be allowed to quit the installer as a result, and for the ones that we are putting the user into pause state for, why the hell not just retry ourselves a couple of times and then hard fail if it persists? I see no point in making the user click a button until we have, on our own, tried the operation a couple of times. If we are getting response codes back, then we have a connection, and it's not like we need the user to plug in the network and hit resume or something. Error handling in http is bad enough that we should consider not exposing this feature until it gets fixed.
Assignee: ssu → syd
Target Milestone: --- → mozilla0.9.3
Target Milestone: mozilla0.9.3 → mozilla0.9.4
moving out to mozilla 1.0
Target Milestone: mozilla0.9.4 → mozilla1.0
nsbeta1+ issues for Win Installer
nsbeta1- per ADT/XPInstall triage.
Keywords: nsbeta1+ → nsbeta1-
Please update this bug with an [adt1] - [adt3] impact rating (or take it off the list if it doesn't even rate adt3.) Thanks!
macos9.0.4, custom spin. I grabbed my build from komodo, and ran it. because ftp is no longer an alias for komodo, the files had not replicated to ftp.mozilla.org. so i tried to install, it didn't tell me what file it was trying to installer, after a while it just switched to pause mode. (cancel) was disabled. it took me a while to figure out that I could do file>quit. I should have been told: 1. what file the app was trying to get 2. when it failed, why it failed And, I should have been able to click (cancel) C. It might also be nice (well, maybe not), to let me select an alternate server/path. [I'll file an RFE unless someone indicates it's already filed]
Target Milestone: mozilla1.0 → ---
is this still a problem on Windows? On linux, the error message isn't particularly descriptive (or even correct), but it does show one and retries several times before giving up.
Assignee: slogan → nobody
OS: All → Windows XP
Hardware: All → PC
Seamonkey and Firefox are using a new NSIS based installer. resolving this old bug, please reopen if you still get this with the new installer
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.