Description
Urls with %2f behave different (apache server error) than with / or _2f.
Related links:
Example
Details
MoinMoin Version |
1.2.3+, 1.3 dev |
Server Setup and Version |
Apache 2.0.50 |
Discussion
This is a security feature of apache. URL with %2f are not allowed.
There is no reason to use %2f when you can use /. Our links do not produce %2f so thats no problem.
Apache allows "/" but not "%2f" ? That seems silly. Why ?
(EditHint: Responding with "They just do, OK?" -- http://www.apacheweek.com/issues/02-11-08 is unsatisfying. I need a link to a better response. )
more discussion
(Should I make a new CategoryMoinMoinBug page for this suggestion ? Just the "Urls with %2f behave different (apache server error) than with / or _2f." is the only bug that is closed.)
Suggestion: make MoinMoin use the W3C standard URI encoding. See http://www.w3.org/International/O-URL-code.html , http://www.w3.org/Addressing/URL/4_URI_Recommentations.html
For example, "#" should be encoded "%23", not "_23". (In particular, the wiki page "List GFM #2" now has the URI http://flashmob.wiki.taoriver.net/moin.cgi/List_20GFM_20_232 )
-- DavidCary
Also, I wish MoinMoin converted " " (blank space) in a [forced link] to "_" when it builds the rendered HTML URI,rather than requiring this non-standard "_20".
That must have been an old version of MoinMoin -- its seems to work correctly now.
I wish MoinMoin collapsed all of "_", "%20", and "%5F" in a requested page name to "_" in the actual page name.
Plan
- Priority:
- Assigned to:
- Status: Closed