You're right that something might be wrong with the client callback or bypass configuration. I had it already working before, but since I made some changes, it does not behave as expected.
The reason why I believe that something must be cached is that I had created before two patterns in the clientCallback node. Those worked fine, they redirected to my login page. I deleted those two patterns and created some new ones - on the author instance, and activated the changes to the public instances. My tests show that my original patterns are still in effect and redirecting to my own login. Patterns that shouldn't be matching any filters anymore (since I deleted them) are still in effect. I disabled the cache filter in all the instances (adding a node enabled=false, type Boolean) but I still see the same behavior. Any other ideas? :( Thank you, Claudia Jan Haderka-2 wrote: > > If the users are redirected to the Magnolia login page instead of yours I > would be more inclined to think issue is in the configuration of the > client callbacks or bypasses in the uriSecurityFilter. This filter is > executed before the cache so it should not be affected by cache. > Jan > -- View this message in context: http://old.nabble.com/URI-Security-cache-tp31214633p31221765.html Sent from the Magnolia - User mailing list archive at Nabble.com. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
