Closed
Bug 15200
Opened 27 years ago
Closed 26 years ago
[BLOCKER] file url with no network access doesn't load
Categories
(Core :: Networking, defect, P3)
Tracking
()
CLOSED
WONTFIX
M13
People
(Reporter: karnaze, Assigned: dougt)
References
()
Details
The page never loads and the throbber keeps going. The page has no http
images. I even removed the http anchors and it made no difference. So, there is
no network access. This is a table regression test. This was not a problem on
9/22.
Updated•27 years ago
|
Summary: [BLOCKER] file url with no network access doesn't load → [BLOCKER] file url with no network access doesn't load
Comment 1•27 years ago
|
||
It works for me if I use the full path with / instead of \ (under linux) and the
file scheme. If it is simply used as stated above mozilla trys to make a http
connect to the host mozilla with layout ... as path or something like that. Is
this supposed to work?
| Reporter | ||
Comment 2•27 years ago
|
||
Sorry for the confusion. The page was loaded as:
file:///s:/mozilla/layout/html/tests/table/bugs/bug10633.html
Updated•27 years ago
|
Assignee: gagan → rpotts
Comment 3•27 years ago
|
||
Rick, This is the "add timeouts to socket transport" bug that we discussed
today. I don't see a bug report for it off hand.
Comment 4•27 years ago
|
||
I'm marking this bug as depending on bug #7428 which is the socket timeout
bug... It sounds like something else is going on here too...
We shouldn't be making any socket connections to load a local page !!
Updated•26 years ago
|
Assignee: rpotts → warren
Comment 5•26 years ago
|
||
hey warren,
I can't figure out what the nsFilePath is doing to file:// URLs :-( This is
what seems to be going on...
1. /mozilla/layout/html/tests/table/bugs/bug10633.html is passed into
the nsFilePath constructor.
2. nsFileSpecHelpers::UnixToNative(...) is called and *removes* the initial '/'
and converts all slashes...
3. nsFileSpecHelpers::Cannonify(...) is called. However, the path is now
mozilla\layout\html\tests\table\bugs\bug10633.html so it assumes it is a
relative path and prepends S:\DIST\WIN32_D.OBJ\BIN to the path :-(
4. Now things are *really* messed up!
How did this ever work? I'm giving you the bug, since I know nothing about this
nsFileSpec stuff...
Updated•26 years ago
|
Assignee: warren → dougt
Target Milestone: M12
Comment 6•26 years ago
|
||
Sounds like part of dougt's nsIFile stuff.
Updated•26 years ago
|
Target Milestone: M12 → M13
Comment 7•26 years ago
|
||
Doug isn't going to get to this in M12. nsIFile may or may not have this
problem, but no one's going to touch nsFileSpec.
Bulk move of all Necko (to be deleted component) bugs to new Networking
component.
| Assignee | ||
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Comment 10•26 years ago
|
||
this was a nsFileURL problem. Since necko will now use nsILocalFile to do
this, I am going to mark as WONTFIX,.
You need to log in
before you can comment on or make changes to this bug.
Description
•