Closed Bug 154798 Opened 23 years ago Closed 23 years ago

Proxy: "No proxy for:" field does not like hosts with numeric characters

Categories

(Core :: Networking, defect)

x86
Windows 2000
defect
Not set
minor

Tracking

()

VERIFIED INVALID

People

(Reporter: ehsmeng, Assigned: darin.moz)

Details

(Keywords: testcase)

Attachments

(1 file)

Hi! Seems to be bug interpreting the data found in Edit/Preferences/Advanced/Proxies, the field for "No proxy for". If I type "macgyver" ..no proxy is used for macgyver. But If I only type "gaxtst21" or "macgyver,gaxtst21", it does not work. It used to work but it doesn't anymore. Is it perhaps because of the numeric caracters in gaxtst21? Kind regadrs, Marcus
I don't know. Can you try w/ a FQDN (gaxtst21.domain.com)?
Blocks: 48718
Summary: "No proxy for:" field does not like hosts with numeric characters → Proxy: "No proxy for:" field does not like hosts with numeric characters
It does work fine if I write gaxtst21 with the domain; e.g gaxtst21.bsstest.gbg.ehpt.com (it's not visible outside ericsson). It doesn't matter if gaxtst21 is in "No proxy for". In the tests with macgyver and gaxtst21 already described, I did not have anything else in this field. /Marcus
Blocks: 172083
No longer blocks: 48718
"no proxy for" is intended as a list of domains. in other words "no proxy for: abc" would not prevent proxying to "abc.foo.com". marcus, can you please check what URL you are loading when you only have "gaxtst21" in your "no proxy for" preference. my suspicion is that you are either directly or indirectly (via a redirect) loading http://gaxtst21.bsstest.gbg.ehpt.com/. if you want to know for sure, you can enable these environment variables before running mozilla: set NSPR_LOG_MODULES=nsHttp:5 set NSPR_LOG_FILE=c:\http.log then if you upload c:\http.log to this bug, we can determine exactly what URLs are being loaded.
Assignee: new-network-bugs → darin
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Hello, They have rearranged the network lately. The file above is irrelevant. I therefore cannot determine anymore if this error remains, is fixed or was a complete misunderstanding from my point. I have a recollection of testing it in IExplorer where it worked but this was a couple of months ago, before the local DNS:es, network etc was changed. Sorry for this, Marcus
VERIFIED/invalid. Can you recall what happened when you said "it didn't work?" Darin is probably too busy to read the log right now, but from what I can tell, you first attempt uses: http://gaxtst21 w/ no proxy, so that works correctly. For some reason, that connection fails to work 0[284010]: >> creating new connection... 0[284010]: Creating nsHttpConnection @1e25a10 0[284010]: nsHttpConnection::Init [this=1e25a10] 0[284010]: nsHttpHandler::DispatchTransaction_Locked [trans=1ddea58 conn=1e25a10] 0[284010]: nsHttpConnection::SetTransaction [this=1e25a10 trans=1ddea58] 1752[f91010]: nsHttpTransaction::OnStatus [this=1ddea58 status=804b0003] 1752[f91010]: nsHttpConnection::OnStartRequest [this=1e25a10] 1752[f91010]: nsHttpConnection::OnStopRequest [this=1e25a10 ctxt=0 status=804b001e] 1752[f91010]: nsHttpConnection::OnStartRequest [this=1e25a10] 1752[f91010]: nsHttpConnection::OnStopRequest [this=1e25a10 ctxt=1e25a14 status=804b001e] 1752[f91010]: nsHttpTransaction::OnStopTransaction [this=1ddea58 status=804b001e] 1752[f91010]: nsHttpHandler::ReclaimConnection [conn=1e25a10(gaxtst21:80) keep-alive=0] 1752[f91010]: closing connection: connection can't be reused 1752[f91010]: active connection count is now 0 1752[f91010]: nsHttpHandler::ProcessTransactionQ_Locked 1752[f91010]: >> unable to process transaction queue at this time so the browser goes back and tries: http://www.gaxtst21.com via a proxy, which responds w/ an error: 1752[f91010]: HTTP/1.1 502 Bad Gateway I've done some poking to verify the string matching works for numeric characters as well. There might be a real problem that related to your config of that system, but I think the original problem description is not a mozilla problem. However, I did find this behavior curious, so I filed bug 190324. I will make a hostname w/ characters a testcase in my proxy tests for "no proxy", so if this is a real problem, we will catch it again before shipping anything.
Status: RESOLVED → VERIFIED
Keywords: testcase
No longer blocks: 172083
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: