Revision 8014
Added by Aaron Marcuse-Kubitza almost 12 years ago
| .htaccess | ||
|---|---|---|
| 36 | 36 |
# this is needed because mod_rewrite often runs the same rules again |
| 37 | 37 |
RewriteRule ^.*[^/]$ $0/ [discardpath,noescape] |
| 38 | 38 |
|
| 39 |
# remove all [] escapes (but leave empty []), e.g. a/[b.c]/ -> a/b.c/
|
|
| 40 |
RewriteRule ^(.*)\[([^\[\]]+)\](.*)$ $1$2$3 [discardpath,noescape,next]
|
|
| 39 |
# remove all [] escapes, e.g. a/[b.c]/ -> a/b.c/ |
|
| 40 |
RewriteRule ^(.*)\[([^\[\]]*)\](.*)$ $1$2$3 [discardpath,noescape,next]
|
|
| 41 | 41 |
|
| 42 | 42 |
|
| 43 | 43 |
# non-filesystem paths |
Also available in: Unified diff
web/main/.htaccess: translate dotpaths: remove all [] escapes: Also remove empty [] to allow permalinking clients to easily generate escaped strings by URL-encoding the value and enclosing it in [], which will now also work even if the value is empty. This change will break any destination URLs that use "[]", such as PHP scripts that use this to indicate an array variable in the query string. In these URLs, the [] must now be %-encoded.