[MAGNOLIA-614] going from edit page to admincentral results in inability to activate content Created: 20/Dec/05 Updated: 23/Jan/13 Resolved: 17/May/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface |
| Affects Version/s: | 2.1.1 |
| Fix Version/s: | 3.0 RC1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Boris Kraft | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
FF 1.0.5 on OSX 10.3 |
||
| Attachments: |
|
| 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 |
this results in http error 400 and inability to activate the page I have not tested this on newer versions of Magnolia, but did not see it documented in jira either. |
| Comments |
| Comment by Francois Bertrand [ 31/Dec/05 ] |
|
Hi: I think this problem is related to the authorization header not returned by firefox. I upload a file with a Tomcat's RequestDumperValve log file to show why I think it is so. n line 2 the request to /autor/menu/inicio/bannerLista/0/headerImage/banner.servicio_civil.jpg (a jpg image in my author webapp) receive the authorization header (see line 19). Then there is a request to /favicon in line 47 that gets "sendredirected" in line 85 to my public home-page (/portal/menu/inicio.html from /portal which is my public web-app). After this request, the browser doesn't send back the authorization header anymore. In line 1564 begins the call to the activation (/autor/.magnolia/adminCentral/extractTree.html), without the authorization header. The activation handler (/portal/ActivationHandler) gets called at line 1609 with an invalid authorization header: see line 1615. Then the ActivationHandler use an empty authorization header to authenticate and fail. Am I right? |