OK, I found the solution. Certainly it was completely unrelated to cache configuration. I had to restart the public instances for the changes in URISecurity filter to take effect. The callback configuration was fine; it was just a matter of restarting the instances.
I did not attempt restarting the instances before, since I have to ask the IT department to do it and I wanted to avoid it if it was not absolutely necessary. Thanks! Claudia Jan Haderka-2 wrote: > > > exactly my point - if switching off the cache doesn't fix the issue, it is > not caused by cache. Maybe you can try to post the callback configuration > somewhere on pastebin.com or similar so others can look at it too. > > Cheers, > Jan > -- View this message in context: http://old.nabble.com/URI-Security-cache-tp31214633p31222105.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]> ----------------------------------------------------------------
