[MAGNOLIA-245] Failing second access to secured page on public instance Created: 14/Dec/04 Updated: 23/Jan/13 Resolved: 17/Dec/04 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 2.0 Final |
| Fix Version/s: | 2.0.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Mirko Brandner | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows XP |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
Hallo, I think I found a new bug with a failing second access to a secured page on public instance. What I did: THE EFFECT: from then on, no second access to the secured page is possible. Except for public's restart. MY WORKAROUND as proposed by Ralf Hirning:
Wonder what you guys will come up with Regards, Mirko |
| Comments |
| Comment by Ugo Cei [ 15/Dec/04 ] |
|
I have the same problem even if there is no authentication. On the "public" instance, only the first access to a page succeeds, following accesses get only a blank page and the following stacktrace in the logs: org.apache.slide.jcr.core.NodeImpl 07.12.2004 13:28:09 – ERROR – failed to resolve path relative to / |
| Comment by Sameer Charles [ 15/Dec/04 ] |
|
Ugo, your problem is not the same. problem with secured URI, I tested again and seems to work, but ll test on windows server. |
| Comment by Ugo Cei [ 15/Dec/04 ] |
|
I set the value for the /server/cache/level1/domain node to the hostname of the public instance, both with and without http:// in front, but I still get the same blank page and stacktrace. |
| Comment by Ugo Cei [ 15/Dec/04 ] |
|
Now I got it to work, somehow, by disabling the cache. I still get the stacktrace but the page is shown. The problem now is that it is very slow. |
| Comment by Sameer Charles [ 17/Dec/04 ] |
|
I dont think there is any bug. perhaps same problem as other people had with wrong domain in cache mappings. |