Dispatcher filters & mod_rewrite
i working on issue yesterday, , realised caused error in dispatcher filters.
the developer had (understandably) expected filters 'see' url passed down preceding handlers (ie mod_rewrite). however, described in documentation, not case:
since dispatcher 4.0.11 no longer necessary set dispatcheruseprocessedurl 1 (in httpd.conf when using apache).
the filter section applied unprocessed, sanitized url, received web server.
this got me thinking - behaviour we'd want dispatcher?
doesn't force open filters wider need to... example, if follow technique described in link below (effectively resolving mapped content paths in apache using mod_rewrite) you'd still have allow * filters wouldn't applied resolved content paths (ie /content/mysite/...).
http://dev.day.com/content/kb/home/cq5/cq5systemadministration/howtoflushmappedcontent.htm l
if filters worked on processed urls allow /content/mysite/* seems lot neater me.
does else thing seems bit odd? missing (ie reason work in way)?
please use latest dispatcher version 4.1.2 works on processed url.
More discussions in Archived Spaces
adobe
Comments
Post a Comment