[EXTDAM-262] DamDownloadServlet do not work for S3 assets Created: 23/Apr/21  Updated: 22/Feb/22  Resolved: 22/Feb/22

Status: Closed
Project: External DAMs
Component/s: None
Affects Version/s: 1.0.5
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Evzen Fochr Assignee: Dominik Maslanka
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 10m
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by EXTDAM-299 DamDownloadServlet do not work for S3... Closed
is cloned by EXTDAM-301 DamDownloadServlet do not work for S3... Closed
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)
[ ]* check BYNDER connector for same issue
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Story Points: 3

 Description   

Steps to reproduce

  1.  try to access s3 asset through DamDownloadServlet
  2.  

.. Logs, screenshots, gifs...

Expected results

asset is downloaded

.. Justify non-trivial expectations with a link to a doc or a relevant discussion.

Actual results

SC_NOT_FOUND = 404 is sent to client

Workaround

Development notes

info/magnolia/dam/core/download/DamDownloadServlet.java:262 expect PathNotFoundException if asset is not found by path without extension. S3AssetProvidet create new empty asset without contentStream, so no try for getting by path with extension is done.
info/magnolia/dam/core/download/DamDownloadServlet.java:161

Remove DamDownloadServlet from cloud branch.



 Comments   
Comment by Dominik Maslanka [ 22/Feb/22 ]

Makes sense - also what Simon wrote above there if we want to be cloud then there is no need. Closing that one.

Generated at Mon Feb 12 01:53:28 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.