[MGNLSLOCK-18] 403 error handling Created: 22/Dec/11  Updated: 14/Mar/12  Resolved: 05/Jan/12

Status: Closed
Project: Magnolia Soft Locking Module
Component/s: None
Affects Version/s: 1.0.4
Fix Version/s: 1.0.5, 2.0

Type: Bug Priority: Neutral
Reporter: Jan Haderka Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File screenshot.tiff    
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   

Current trunk produces weird error and renders login screen when Magnolia responds with 403 (not really sure how I got there, sorry).



 Comments   
Comment by Federico Grilli [ 28/Dec/11 ]

I managed to reproduce it by chance when restarting EE webapp in eclipse and while a demo-project page was open and kept on doing ajax requests to the server. I'll add an explicit error handler for 403 as I do for other error codes, so to handle this in a more graceful manner.

Generated at Mon Feb 12 07:14:32 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.