264779 - Question mark interpreted in file:/// URLs

Status: RESOLVED DUPLICATE of bug 102603

(Core :: Networking: File, defect)

Description

[Felix Wiemann]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041017 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041017 Firefox/0.10.1

The question mark occuring in file:/// URLs is interpreted, but as far as I can
see from RFC 1738, it shouldn't because it has no special meaning for file:/// URLs.

Reproducible: Always
Steps to Reproduce:
1. Create a file with a name containing a question mark, e.g. "foo?bar"
2. Enter the location of the file in the location bar, e.g.
   file:///home/felix/tmp/foo?bar
Actual Results:  
Firefox tries to open the file with anything after the '?' stripped.  In the
example above, it would try to open "file:///home/felix/tmp/foo".

Expected Results:  
Firefox should have opened "file:///home/felix/tmp/foo?bar".

This behavior is especially annoying when recursively downloading files with
wget, for example, because wget leaves the question mark in both links and file
names.  Firefox, however, requires the question mark to be escaped with %3F in
links.

Comment 1

[Ben Fowler]

Suggest reading comments in Bug 102603 this (only) might be a dup.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 4

[Felix Wiemann]

This problem still persists in Firefox 1.5.

Comment 5

[José Jeria]

Did  you see/read comment 1?

Comment 6

[Kevin Brosnan]

*** This bug has been marked as a duplicate of 102603 ***

Comment 7

[benc]

V/dupe.