Closed Bug 544685 Opened 15 years ago Closed 14 years ago

XML Parsing Error: not well-formed when directory contain file.ext?xx&yy

Categories

(Core :: Networking: File, defect)

1.9.2 Branch
x86
Linux
defect
Not set
major

Tracking

()

VERIFIED DUPLICATE of bug 525222

People

(Reporter: janakawicks, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 This is with regards to file:// it gives an "XML Parsing Error: not well-formed" when the folder has a file with the following name <filename>.<ext>?<some value>&<some value> e.g. myfile.txt?param1&param2 <-- Issue myfile?param1&param2 <-- OK Reproducible: Always Steps to Reproduce: 1. cd /tmp 2. wget -c "https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&format=guided" 3. file:///tmp/ Actual Results: XML Parsing Error: not well-formed Expected Results: Should list the files as normal
I've been able to reproduce this bug using Firefox 3.6.3 (ubuntu 10.4) with the filename of ".&". Here's howto reproduce very quickly: touch .\& firefox $(pwd)
http://www.aspca.org/ crashes with a similar message: XML Parsing Error: not well-formed Location: http://www.aspca.org/ Line Number 21, Column 116:<iframe src="http://img-cdn.mediaplex.com/0/15312/universal.html?page_name=aspca_homepage_master_tag&ASPCA_Homepage=1&mpuid=" HEIGHT=1 WIDTH=1 FRAMEBORDER=0></iframe> ------------------------------------------------------------------------------------------------------------------- In contrast Safari displays the page. Surprisingly, firefox displays it ok too!
Component: File Handling → Networking: File
Product: Firefox → Core
Version: unspecified → 1.9.2 Branch
QA Contact: file.handling → networking.file
URL-escaping won't escape random HTML crud. In any case, this is fixed in gecko 2.0.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.