Closed Bug 72814 Opened 24 years ago Closed 24 years ago

Download options screen: select http option gives network error

Categories

(SeaMonkey :: Installer, defect)

x86
Windows NT
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: agracebush, Assigned: ssu0262)

Details

Steps to reproduce: 1. download installer (using build 2001032106) 2. proceed through wizard screens to download options 3. choose 'use http' actual results: network error when trying to download xpcom.xpi expected results: all files downloaded
Well, now *there's* a problem. sweetlou doesn't appear to have an equivalent HTTP server the way ftp.netscpae.com and ftp.mozilla.org do, so the ftp/http switch doesn't make a lot of sense in that case. Since this is designed for our external customers we could mark this WONTFIX and make just something internal folks will have to deal with. Of course that means it's not going to get a lot of testing, until we get mozilla.org hosting the downloader. This also suggests the ftp/http UI should be switchable from the config.ini because some folks won't want it for their re-packaged Mozilla. But if we're getting rid of redirect.ini and replacing it with fall-back URLs maybe we could handle the ftp/http silently: URL0=ftp://ftp.netscape.com/etc URL1=http://ftp.netscape.com/etc URL2=ftp://sweetlou/etc This has a big drawback when some folks may just *know* ftp isn't going to work fromt their location. It'd be nice if they didn't have to wait for ftp to fail (or worse, sort of work but really suck). CC'ing folks to gather additional opinions.
I was wondering when you were going to try the HTTP button :) The problem is that there isn't an HTTP server for the daily builds. The way the server would have to be setup is: ftp: ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/[date] http: http://sweetlou/products/client/seamonkey/windows/32bit/x86/[date] notice that sweetlou would have to support both ftp:// and http:// with the same paths. I don't know if this is possible on sweetlou. Adding chofmann to the cc: list since it's his wife.
QA Contact: gemal → gbush
No comment on my suggestion that we simply hide the feature as a fallback URL? Can the UI be easily hidden for folks who ship re-packaged Mozilla from servers which don't support http? (or vice versa, don't support ftp?).
yes, in the config.ini simply set the following: [Dialog Download Options] Use Protocol Settings=DISABLED to show or not show the radio buttons. You can also set the protocol type which is independent of whether or not the buttons are shown. To change the protocol type, set the following: [Dialog Download Options] Use Protocol=FTP ; or HTTP. default is FTP if not set.
Status: NEW → ASSIGNED
Use carbuncle.mcom.com:8080 The feature works, I configured a proxy server to map http: to ftp:, and since the paths on sweetlou are the same, I can confirm I loaded: Win32 2001-03-19-04 with it. I haven't figured out what you guys are supporting w/ Mac. If you want me to test it, let me know. Since "ftp proxy" is really "send FTP URLs over HTTP proxy requests" the returned payload is the same (and works!). Since HTTP supported for proxy only at this point, you sort of can get out adding a web server to sweetlou...
dveditz wrote: <<No comment on my suggestion that we simply hide the feature as a fallback URL?>> I think it's probably the right thing to do for the commercial build (hide the UI). Mom and Dad really don't need to see this. However, it's totally appropriate for the Moz build.
Kevin, The UI is in the "Advanced" dialog (which mom and dad may not bother with anyways, right?).
If it's in "Custom" then you're right. My bad.
I think we need to support HTTP URL'd HTTP proxy in commercial because of the problems I had when I reopened bugscape 39015 HTTP URL's seem, IMO, the best choice for a default proxy selection.
marking invalid. sweetlou does not support http, only ftp. mozilla.org is already hosting the stub installer too, so we can test http as well as ftp.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
verify
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.