Closed
Bug 1376524
Opened 7 years ago
Closed 7 years ago
Logs show incorrect handling of null hostname in nsHostResolver::ResolveHost
Categories
(Core :: Networking: DNS, defect)
Core
Networking: DNS
Tracking
()
RESOLVED
INVALID
People
(Reporter: valentin, Assigned: valentin)
References
Details
(Whiteboard: [necko-active])
The logs in attachment 8879880 [details] show: [ProxyResolution]: D/nsHostResolver Resolving host [null]. [ProxyResolution]: D/nsHostResolver No usable address in cache for host [null]. However, that method should return if host is null: NS_ENSURE_TRUE(host && *host, NS_ERROR_UNEXPECTED); http://searchfox.org/mozilla-central/rev/b425854d9bbd49d5caf9baef3686e49ec91c17ec/netwerk/dns/nsHostResolver.cpp#737 I'm not sure this is the cause of bug 1174249, but it seems a weird behaviour.
Assignee | ||
Comment 1•7 years ago
|
||
I just seem to have misread the logs. The string in the logs is "null", not "(null)", so this is just some webpage trying to resolve "null" as a host. Weird, but not a bug.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•