Edit report at https://bugs.php.net/bug.php?id=63769&edit=1
ID: 63769
Updated by: ab@php.net
Reported by: hanskrentel at yahoo dot de
Summary: file:// protocol does not support percent-encoded
characters
Status: Not a bug
Type: Bug
Package: Streams related
Operating System: Windows
PHP Version: 5.4.9
Block user comment: N
Private report: N
New Comment:
@hanskrentel
That's my test:
- create file 'catalog%202.xml' with content "percent filename"
- create file 'catalog 2.xml' with content "space filename"
- then run
php -r "echo file_get_contents('file://C:/my/path/catalog%202.xml');"
percent filename
- then run
php -r "echo file_get_contents('file://C:/my/path/catalog 2.xml');"
space filename
That's pretty straight forward. That's what I mean - no decoding, both are valid
filenames. The decoding should be done in your app depending on what it needs. In your example - you
create 'catalog 2.xml' and are trying to stat 'catalog%202.xml', literally. But
'catalog%202.xml' doesn't exist.
Previous Comments:
------------------------------------------------------------------------
[2013-01-06 07:03:56] anon at anon dot anon
Actually, hold on a sec, plus signs are *not* supposed to be decoded here. That means that file
names containing plus signs would not be broken by a fix, and only file names containing a
'%xx' (where x is a hexit) sequence would be affected, which is probably uncommon. Perhaps
you have a chance.
------------------------------------------------------------------------
[2013-01-06 06:38:45] anon at anon dot anon
>You would have wanted to access it via 'file:///C:/temp/catalog%%25202.xml'
Actually, 'catalog%25202.xml', but I know, I'm agreeing with you. I'm just
pointing out that this erroneous behavior may be depended on somewhere in some PHP script, where the
author, in good faith, did whatever made things work. I assume you're going to pass your path
through urldecode (or not encode it in the first place), and then you'll be one of them.
In any case, you're unlikely to get any support here. The reviewers here don't do much
except dismiss things as 'Not a bug' and once they've successfully done that they
lose interest. C'est le PHP.
------------------------------------------------------------------------
[2013-01-06 01:29:30] hanskrentel at yahoo dot de
If you would create a file named
catalog%202.xml.
You would have wanted to access it via:
'file:///C:/temp/catalog%%25202.xml'
which as well does not work. I'm not doing a bug report here to be treated like
an idiot. I better suggest you piss completely off
instead of leaving such an idiotic comment. My 2 cents.
------------------------------------------------------------------------
[2012-12-20 16:27:43] anon at anon dot anon
>The path "file:///C:/temp/catalog%202.xml" (without the quotes) does *not* work.
Unfortunately it does work, if you create a file literally named catalog%202.xml. PHP's
behavior is broken but it's impossible to alter it without breaking compatibility.
------------------------------------------------------------------------
[2012-12-17 14:55:51] hanskrentel at yahoo dot de
I beg your pardon, but if both are perfectly valid filenames, the fs function
behaviour is broken (and not correct), because it does not work with both
perfectly valid filenames:
The path "file:///C:/temp/catalog%202.xml" (without the quotes) does *not* work.
The request is to remove this shortcoming and have it work. I thought this was
clear from the initial report. Please let me know how I can further assist with
this.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=63769--
Edit this bug report at https://bugs.php.net/bug.php?id=63769&edit=1