[MGNLDAM-350] DamManager logs warning even though asset is later found Created: 25/Nov/13  Updated: 23/Jun/14  Resolved: 23/Jun/14

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: 1.2
Fix Version/s: 2.0.1

Type: Bug Priority: Neutral
Reporter: Tobias Mattsson Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

DamDownloadServlet has a fallback to try when a path is not found, when this succeeds a warning has already been logged. The log is confusing warning about problems that are actually not problems.

The logging is in info.magnolia.dam.DefaultDamManager#getAssetForPath

To reproduce request the following asset: http://localhost:8080/magnoliaAuthor/dam/demo-project/downloads/Magnolia_Flyer_4-0/Magnolia%20Flyer%204.0.pdf



 Comments   
Comment by Eric Hechinger [ 23/Jun/14 ]

Solve with the 2.0 release

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