Last modified: 2011-03-24 03:04:38 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 9204 - Slash (/) entered as %2F causes 404 file not found error
Slash (/) entered as %2F causes 404 file not found error
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
PC All
: Normal normal with 2 votes (vote)
: ---
Assigned To: Rob Halsell
: shell
: 9205 11735 17389 (view as bug list)
Depends on: 17452
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-07 10:29 UTC by Luke Boyling
Modified: 2011-03-24 03:04 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Luke Boyling 2007-03-07 10:29:02 UTC
I've got a Firefox keyword search bookmark created (so that when i type "wpgo
Main Page" it will take me to the enwiki Main Page). This works fine if the page
is not a subpage. However, when it is, Firefox replaces the / with %2F, colon :
with %3A, etc (in the case of
http://en.wikipedia.org/wiki/User%3AHarryboyles%2FStatus). The %2F causes a 404
file not found error to occur. I'm not sure whether this is a Firefox issue,
Wikimedia issue or MediaWiki issue.
Comment 1 Raimond Spekking 2007-03-07 10:32:27 UTC
*** Bug 9205 has been marked as a duplicate of this bug. ***
Comment 2 Brion Vibber 2007-03-07 23:15:58 UTC
This is a low-level "feature" in Apache.
Comment 3 Brion Vibber 2007-10-24 14:38:51 UTC
*** Bug 11735 has been marked as a duplicate of this bug. ***
Comment 4 Carl Fürstenberg 2007-11-08 22:55:37 UTC
See http://httpd.apache.org/docs/2.0/mod/core.html#allowencodedslashes how to fix this. in my opinion, it should be fixed, as I think there is no security issue here in danger by allowing encoded hashes.
Comment 5 Brion Vibber 2007-11-13 16:04:07 UTC
When we've upgraded every server to Apache 2, we'll take a peek. :)
Comment 6 Roan Kattouw 2007-11-13 16:23:31 UTC
(In reply to comment #5)
> When we've upgraded every server to Apache 2
Do you mean WMF servers still run Apache 1.3? *shock*
Comment 7 P.Copp 2009-02-06 19:31:25 UTC
*** Bug 17389 has been marked as a duplicate of this bug. ***
Comment 8 MZMcBride 2009-02-06 19:33:51 UTC
Reopening.

(1) Makes it easier to find when searching to avoid dupes.
(2) This should probably be looked at again. How far along is the transition to Apache 2?
Comment 9 MZMcBride 2009-02-11 21:17:49 UTC
This blog post details five ways to solve this issue: http://www.jampmark.com/web-scripting/5-solutions-to-url-encoded-slashes-problem-in-apache.html
Comment 10 Brion Vibber 2009-02-11 21:23:44 UTC
Note four of those ways are "don't encode them that way", and one is to use the configuration option in Apache 2 mentioned above to disable the stupid restriction. :)

Complete Apache 2 use is still pending on completion of the Ubuntu migration -- filing this as bug 17452 so we have it in the dependency tree.

*After* the migration is completed we can go ahead and disable the check. Until then it should remain on so behavior will remain consistent.
Comment 11 Sam Reed (reedy) 2010-12-01 18:24:55 UTC
Ping
Comment 12 Tim Starling 2011-03-24 03:04:38 UTC
Done.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links