Closed
Bug 117263
Opened 23 years ago
Closed 23 years ago
Wrong "Host" HTTP header in install through proxy
Categories
(SeaMonkey :: Installer, defect)
SeaMonkey
Installer
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.0.1
People
(Reporter: dolmen, Assigned: dprice)
References
Details
(Whiteboard: [adt1 rtm])
Attachments
(1 file, 2 obsolete files)
2.27 KB,
patch
|
samir_bugzilla
:
review+
dveditz
:
superreview+
jesup
:
approval+
|
Details | Diff | Splinter Review |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.7) Gecko/20011221
BuildID: 2001122106
After experimenting problems with download through a proxy I traced the HTTP
request sent by the windows installer-stub to install Mozilla 0.9.7.
I found out that the "Host" HTTP header has always the value of the proxy host
with HTTP download instead .
This occurs only with HTTP download. No problem with FTP download through the proxy.
Reproducible: Always
Steps to Reproduce:
Set a proxy host/port in the installer.
I traced the HTTP requests with a custom TCP proxy between the installer and a
Netscape Proxy 3.5.
Example:
Proxy host : 192.168.0.1
Proxy port : 8080
The download URL is http://ftp.mozilla.org/...
Actual Results: The "Host" points to the proxy server.
In the exemple:
Host: 192.168.0.1
Expected Results: The "Host" header should point to the host of the URL where
is the file to download.
In the example:
Host: ftp.mozilla.org
The bug is here :
http://lxr.mozilla.org/mozilla/source/xpinstall/wizard/libxpnet/src/nsHTTPConn.cpp#282
The host should be extracted from the mProxiedURL, as for ftp:// URLs, few lines
above.
By the way, I found the nsHTTPConn API quite strange : calling SetProxyInfo with
the URL to download, and the proxy username/password was not obvious. I had
first expected that the URL parameter of SetProxyInfo was the host/port of the
proxy, not the final host.
Reporter | ||
Comment 1•23 years ago
|
||
The bug is here :
http://lxr.mozilla.org/mozilla/source/xpinstall/wizard/libxpnet/src/nsHTTPConn.cpp#282
The host should be extracted from the mProxiedURL, as for ftp:// URLs, (code to
reproduce is just few lines above).
I'm sorry, I haven't a build environment to make/test a patch.
By the way, I found the nsHTTPConn API quite strange : calling SetProxyInfo with
the URL to download, and the proxy username/password was not obvious. I had
first expected that the URL parameter of SetProxyInfo was the host/port of the
proxy, not the final host.
![]() |
||
Comment 2•23 years ago
|
||
confirming, especially since the exact problem has been pointed out!
Updated•23 years ago
|
QA Contact: bugzilla → ktrina
Reporter | ||
Comment 4•23 years ago
|
||
Still in Mozilla 0.9.9 Net installer.
Added in CC endico, 0.9.9 release notes author, as the bug doesn't appear there.
THE CONSEQUENCE OF THIS BUG IS THAT IT IS NOT POSSIBLE TO DOWNLOAD Mozilla
THROUGH Netscape Proxy 3.5 (and probably throug any HTTP proxy) USING THE
Mozilla Net Installer !!!
Reporter | ||
Comment 6•23 years ago
|
||
Still in Mozilla 1.0RC1.
This is a blocking bug with the "Network installer" through a proxy !!!!
No information about the true cause of download problem is reported to the user,
because it is a Mozilla bug. So the user don't know what to do. Personnally I
tried about 10 times before giving up and tracing the HTTP request as specified
in the original bug report.
The only workaround is to download and use the full installer instead of the
light one.
Please, fix this bug for Mozilla 1.0.
Summary: Wrong "Host" HTTP header in install trough proxy → Wrong "Host" HTTP header in install through proxy
Reporter | ||
Comment 7•23 years ago
|
||
Adding mozilla1.0 to raise visibility of this bug.
Keywords: mozilla1.0
-->dprice
Assignee: syd → dprice
Status: ASSIGNED → NEW
Whiteboard: [adt2] → [adt2 rtm]
Assignee | ||
Comment 9•23 years ago
|
||
I am able to use proxy to download and install the mozilla nightly build from
ftp://ftp.mozilla.org/pub/mozilla/nightly/latest-1.0.0/mozilla-win32-installer.exe
I can't get to 192.168.0.1 so I tested with a different server. Could that be
the problem? Please retest and let me know.
Assignee | ||
Comment 10•23 years ago
|
||
duh, used http for download instead of ftp. I can reproduce it now.
Assignee | ||
Comment 11•23 years ago
|
||
Comment 12•23 years ago
|
||
Comment on attachment 84408 [details] [diff] [review]
patch
r=dveditz
Attachment #84408 -
Flags: review+
Comment 13•23 years ago
|
||
Can you provide a trace or logs from the proxy server?
My Netscape Proxy Server has never rejected requests based on any of the various
"Host: line is incorrect bugs" I've worked on...
Assignee | ||
Comment 14•23 years ago
|
||
From your email address I'm guessing you're inside the firewall. I was able to
use the server carbuncle port 8080 to reproduce this.
Comment 15•23 years ago
|
||
Comment on attachment 84408 [details] [diff] [review]
patch
r=sgehani
Comment 16•23 years ago
|
||
Comment on attachment 84408 [details] [diff] [review]
patch
sr=mscott
Attachment #84408 -
Flags: superreview+
Comment 17•23 years ago
|
||
(I'm the administrator of that proxy...)
I understand now. Can someone clarify this aspect in the summary:
This only happens with one of the two modes right (ftp probably...).
FTP and HTTP proxy both use an HTTP connection (they are actually URL proxy of
an ftp:// URL or http:// URL inside HTTP).
I know that one mode seems to have failed a lot for me lately (can't tell b/c I
have to quit to run the installer to see...)
Reporter | ||
Comment 18•23 years ago
|
||
patch.
- code factorised from dprice patch to handle common operations for proxied FTP
and HTTP urls.
- corrects a small bug: variables host and path where not initialized to NULL.
I'm very sorry: this code may not compile as I haven't a build environment to
compile/test this patch.
Assignee | ||
Comment 19•23 years ago
|
||
Thanks for the patch :) It looks much cleaner that what I did. I'll test with
it and get it landed.
Assignee | ||
Comment 20•23 years ago
|
||
fixes a compile error and changes the indent style to match the rest of the
file.
Attachment #84408 -
Attachment is obsolete: true
Attachment #84974 -
Attachment is obsolete: true
Reporter | ||
Comment 21•23 years ago
|
||
The patch is ok.
By the way, I'm distributing my original patch (patch 2) under the NPL/GPL/LGPL
"triple license".
Comment 22•23 years ago
|
||
Comment on attachment 85006 [details] [diff] [review]
patch 3
r=sgehani
Please add a comment mentioning that the port is not overridden if specified
when calling ParseURL().
Attachment #85006 -
Flags: review+
Comment 23•23 years ago
|
||
Olivier: since you're patch is a Modification of the original file you can't
really change the license on the file (which currently is MPL). Are you OK with
us using it as MPL only? mozilla.org is working toward converting the entire
tree, so eventually it'll be switched.
Comment 24•23 years ago
|
||
Comment on attachment 85006 [details] [diff] [review]
patch 3
sr=dveditz, I think the license question is irrelevant here
Attachment #85006 -
Flags: superreview+
Reporter | ||
Comment 25•23 years ago
|
||
dveditz:
According to http://www.mozilla.org/MPL/relicensing-faq.html, the tree is going
to be relicensed to the three licences MPL/GPL/LGPL.
According to http://www.mozilla.org/MPL/license-policy.html :
<BLOCKQUOTE>
The following license is acceptable for both new Mozilla source files and
modifications to existing source files, for any directory in the Mozilla source
tree (except those specified below):
* MPL/GPL/LGPL triple license
</BLOCKQUOTE>
The header of this file (nsHTTPConn.cpp) says the code is currently only
copyrighted by Netscape.
If you force me to release it under only the MPL license, I may one day be a
blocker to relicensing just because I'm not available or dead or....
I don't want to block the relicensing effort. So this is why I proposed to
release the patch under the three licenses. I'm not an expert in licensing
terms, but I just want to not block software from being released under the LGPL/GPL.
So isn't it the good time for Netscape to relicense the file under the three
license just before accepting my patch ?
Or maybe this comments written by myself, telling that I accept MPL/GPL/LGPL
relicensing, will be enough when relicensing time will come for this source file.
Comment 26•23 years ago
|
||
I believe your statement in this bug will be sufficient.
Assignee | ||
Comment 27•23 years ago
|
||
on the trunk
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 28•23 years ago
|
||
using trunk builds for 5/31 and installing both commercial and mozilla apps,
using carbuncle, 8080 for proxy
Windows and Linux give successful downloads and installs.
on Mac OS 9.2, the commercial installer does nothing, the resume button keeps
becoming enabled and I had to force/quit.
the Mozilla installer did download and install but the UI was all messed up.
The first three lines were empty for most of the download- and the progress
showed x kb of 0kb for each component downloaded. After each component
downloaded, I had to press resume. At one point the first line said:
downloading: validating quality feedback agent for a long time.
bottom line: verified on trunk for Linux and Windows but not Mac
Comment 29•23 years ago
|
||
Comment on attachment 85006 [details] [diff] [review]
patch 3
please check into the 1.0.1 branch ASAP. once landed remove the
mozilla1.0.1+ keyword and add the fixed1.0.1 keyword
Attachment #85006 -
Flags: approval+
Updated•23 years ago
|
Target Milestone: mozilla1.0 → mozilla1.0.1
Comment 30•23 years ago
|
||
grace, did you try Mac without using proxy, but with the same installer? How
did it work?
Comment 31•23 years ago
|
||
Yes, I did other installs with same Installer - trunk for 5/31- no problems
Assignee | ||
Comment 32•23 years ago
|
||
I filed bug 149505 to handle the issues raised for the mac. I believe they are
separate from the problem solved in this bug.
Comment 33•23 years ago
|
||
adt1.0.1+ (on the ADT's behalf) approval to checkin to the 1.0 branch. pls check
this in asap, then add the "fixed1.0.1" keyword.
Comment 34•23 years ago
|
||
marking verified on trunk for Linux and Windows
Status: RESOLVED → VERIFIED
Assignee | ||
Updated•23 years ago
|
Keywords: mozilla1.0.1+ → fixed1.0.1
Comment 35•23 years ago
|
||
Mozilla- Linux and Windows branch and trunk builds
Keywords: fixed1.0.1 → verified1.0.1
Comment 36•20 years ago
|
||
*** Bug 183410 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•