Closed
Bug 125445
Opened 23 years ago
Closed 23 years ago
Proxy: proxy->client error displays target hostname in message.
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: raffaelespazzoli, Unassigned)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.6) Gecko/20011120
BuildID: 2001112009
if the configured proxy is unavalible, mozilla report that it can't connect to
the URL you're asking instead to the proxy's URL. This can be misleading and may
require some time to discover the problem. Of course this happen if your
changing often the connection setting, that is unlikely my case.
Reproducible: Always
Steps to Reproduce:
1.configure a wrong proxy : pippo.proxy.com
2.connect to a site : www.amazon.com
3.
Actual Results: www.amazon.com could not be found. Please check the name and
try again.
Expected Results: The proxy pippo.proxy.com could not be found. Please check
the name and try again.
Comment 1•23 years ago
|
||
*** This bug has been marked as a duplicate of 56629 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Comment 2•23 years ago
|
||
+verifyme
reporter:
Would you like to look at the description of the bug Tuukka marked as a duplicate?
If it is the same problem, you can set your bug to VERIFIED, meaning you agree
it is the same problem.
Keywords: verifyme
Reporter | ||
Comment 3•23 years ago
|
||
I agree the bug is the same of Tukka's one.
When do you plan to fix this?
bye
Status: RESOLVED → VERIFIED
Comment 4•23 years ago
|
||
The duplicate is marked for mozilla 1.0.1, which means "first priority after 1.0
is completed."
Some of this worked correctly in the status field of the browser window, so this
is doable, maybe a good starter bug for someone.
Keywords: verifyme
Updated•23 years ago
|
Summary: bad error message → Proxy: proxy->client error displays target hostname in message.
One final comment:
To clarify a point you were making "mozilla report that it can't connect to
the URL you're asking instead to the proxy's URL"
Just so you know, the problem is with the hostname, not the entire URL. The
hostname is only one piece of info in a URL.
You need to log in
before you can comment on or make changes to this bug.
Description
•