[MGNLUI-2426] Reloading page in editor causes 404 Created: 18/Nov/13  Updated: 03/Dec/20  Resolved: 02/Dec/13

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.1, 5.2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Tomcat 7.0.22


Attachments: PNG File page-reloading-issue.png    
Issue Links:
causality
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
Release notes required:
Yes
Sprint: 5.2.1

 Description   

To reproduce

  • open a page in edit mode
  • reload it in browser
    Outcome
  • for each reload the number semi-colons in the location doubles like in a geometric sequence {1,2,4,8,16,…}
  • practically this causes a 404 error (see screenshot)

It looks like the issue is related to the app server. With Tomcat 7.0.47 the problem doesn't occur.



 Comments   
Comment by Federico Grilli [ 29/Nov/13 ]

Stopping progress here as I've been stuck for too long. As far as I could see, the redundant semicolons are not added by some Magnolia class (possible culprits I checked were Fragment and DefaultLocation), rather they seem either to be already in the original request or possibly added by Vaadin in the process of un/marshalling parameters from client to server and viceversa. Adding the debug=true parameter to the application url and reloading a page one can see for instance com.vaadin.client.ui.ui.UIConnector id=300 location=http://localhost:8080/magnolia-enterprise-webapp/.magnolia/admincentral?debug=true#app:pages:detail;;;;/demo-project:edit

Comment by Federico Grilli [ 02/Dec/13 ]

I could not pinpoint in Tomcat's release notes the actual bug fix for it but according to my manual tests it really looks like an issue with the app server before 7.0.47.

Generated at Mon Feb 12 08:56:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.