Details
-
Bug
-
Resolution: Fixed
-
Major
-
2.1.3, 2.1.4, 2.1.5
-
None
-
Windows XP pro, with sp2
JDK 1.5.0_06
Tomcat 5.5.15
Description
Here are steps to reproduce the problem:
1. Let's begin from a clean magnolia. Version doesn't matter, 2.1.3 or 2.1.5 are both ok. Make necessary change to default configuration. Because I am using Tomcat on port 8080, what I need do is changing /subscribers/SubscriberConfig/0001/address to localhost:8080/magnoliaPublic, and /subscribers/SubscriberConfig/0001/senderURL to http://localhost:8080/magnoliaAuthor on author instance. That's all. Make sure activation works.
2. Let's change something. By default, /server/secureURIList for author instance is /, means all request are secured. Let's change / to /m*, AND add another 2, which are /admintemplates/* and /.magnolia/* . So basically, under /server/secureURIList, we will have content node 0001, 0002, 0003, under each, we have node data URI, the values are /m*, /admintemplates/, and /.magnolia/ . I'll explain why I do this later.
3. Let's stop tomcat (or whatever you are using), exit from your browser (for me it's firefox). Then start tomcat and your browser again.
4. You can not activate pages any more.
5. Let's go on. Web develper (http://chrispederick.com/work/webdeveloper/) is really a good tool for firefox. I am using 1.0.2. Click "Cookies -> Clear Session Cookies". Then, you can activate any more again.