Closed
Bug 202219
Opened 23 years ago
Closed 9 years ago
file: URLs ignore hostname, but history does not
Categories
(Core Graveyard :: History: Global, defect)
Core Graveyard
History: Global
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: benc, Unassigned)
References
(
URL
)
Details
STEPS:
Take any file URL you use (most people use the "three slash" format).
Go to URL.
Check history, it will appear under "(no host)".
Change URL to have a "hostname", like example provided above.
Go to URL.
Check history, you will see the URL is filed under the hostname you added.
NOTE:
This problem was mentioned in bug 107153, but not at the time it did not strike
me as a real bug.
I searched for dupes, b/c this happens w/ ftp too, so I figured someone would
have noticed.
Even if there is a "History ignores URL scheme" bug, the problem w/ file: is
special because our file: protocol handler ignores the hostname field.
Comment 1•23 years ago
|
||
> because our file: protocol handler ignores the hostname field
Isn't that just a bug that needs fixing?
Yes. That is bug 70871, I should have mentioned it specifically.
It did occur to me that maybe what should happen is that when people parse a
file: URL, that the hostanem is always returned as NULL, but I'm not sure if
that is the right approach.
Updated•19 years ago
|
Assignee: bross2 → nobody
QA Contact: chrispetersen → history.global
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•