[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Grégory Joseph updated MAGNOLIA-3505:
-------------------------------------

    Comment: was deleted

(was: Sure, let me know how that goes :))

> VirtualURI configurations that lead to 404s seem to be cached
> -------------------------------------------------------------
>
>                 Key: MAGNOLIA-3505
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3505
>             Project: Magnolia
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 4.3.1
>            Reporter: Michael Markowski
>            Assignee: Philipp Bärfuss
>
> I configured a new VirtualURI (regex).
> class   ->   info.magnolia.cms.beans.config.RegexpVirtualURIMapping
> fromURI ->   /search/(.*)
> toURI   ->   forward:/MyPage/de_DE/Search.html?q=$1
> I tested the configuration several times with the following url:
> www.foo.bar/search/ipod
> It did not work (404).
> After I found the problem (typo), I fixed the configuration, but it was not 
> possible to access www.foo.bar/search/ipod anymore.
> Slightly different URLs like www.foo.bar/search/ipod2 or 
> www.foo.bar/search/iphone worked.
> I restarted magnolia, problem persisted.
> I assumed that the 404 would be cached by magnolia and deleted the cache 
> directory and restarted again, then it worked.
> From my point of view, 404's in VirtualURI mappings should not be cached (at 
> least not forever) by magnolia.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to