[MAGNOLIA-7246] Aggregator filter throw servlet exception when calling any invalid URL Created: 18/Jan/18  Updated: 22/Jan/18  Resolved: 22/Jan/18

Status: Closed
Project: Magnolia
Component/s: core, rendering
Affects Version/s: 5.6.1
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Viet Nguyen Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
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
Date of First Response:

 Description   

Symptom:
As described in SUPPORT-8316 and Karel described for requests such as 'https://www.magnolia-cms.com/.imaging/heya' which point to non existing resources or invalid URL:

When calling an invalid URL we get an error 500.
I would assume that the result should be a 404. Why do we get a 500. Following the execption it looks like this is cause directly inside the AggregatorFilter.

Expected result:
Correctly return HTTP error code
Provide 'Default error pages for public instances' (why not also author instance) – ONDEMAND-1448



 Comments   
Comment by Jan Haderka [ 22/Jan/18 ]

The HyperText Transfer Protocol (HTTP) 500 Internal Server Error server error response code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.

This error response is a generic "catch-all" response. Sometimes, server administrators log error responses like the 500 status code with more details about the request to prevent the error from happening again in the future.

This is correct response and the default page for such errors. Anyone can customize is, similar as for 404 pages.
In case servlet POV such url is valid, only you know that you didn't upload such image. Imaging servlet just realizes that it failed to process requested imaging chain and thus returns 500 (internal error).

Generated at Mon Feb 12 04:22:04 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.