Closed Bug 98877 Opened 24 years ago Closed 24 years ago

jar:file:// incorrectly parses certain internal html links in a zip file

Categories

(Core :: Networking: File, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 97682

People

(Reporter: phoenixreads, Assigned: dougt)

Details

I compressed an html-based e-book and did an experiment to test relative URLs in the file and found the following error. The directory structure is... [base dir] toc.html /ch01 page1.html While displaying [base dir]/ch01/page1.html there was a reference to [base dir]/toc.html Which end up being changed to [base dir]/ch01/..toc.html Checked the original zip file and link remain unchanged and is read as such with just 'file://'
Nothing to do with html parser. giving to netlib
Assignee: harishd → dougt
Component: Parser → Networking: File
QA Contact: bsharma → benc
I don't know much about jar, but I think you are saying it should be: [base dir]/ch01/../toc.html Which would be compressed per RFC 1630 into: [base dir]/toc.html
I believe this will be fixed by the checkin for bug 97682, so I'll add this as dependent and let you confirm if it works.
Depends on: 97682
No longer depends on: 97682
fix for bug 97682 is checked in. Pull netwerk/base/src/nsIOService.cpp or wait for tomorrows build and test if this is also fixed.
Depends on: 97682
phoenixreads: Please take a newer build and test again. If it's good, please mark it VERIFIED. I've marked this bug a duplicate, because JAR is the only place this bug would show up. *** This bug has been marked as a duplicate of 97682 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
No longer depends on: 97682
+verifyme I'm barely jar-literate, so I'm leaving it open for verification. If I ever grow a brain, I'll come back to this.
Keywords: verifyme
VERIFIED/dupe re-read the other bug, and I'm reasonably confident this is fixed by that bug. Please reopen if this does not work.
Status: RESOLVED → VERIFIED
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.