[EXTDAM-327] Error loading Bynder Assets with special Characters in it (|) Created: 02/Dec/21  Updated: 18/Oct/22  Resolved: 18/Jan/22

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

Type: Bug Priority: Major
Reporter: Pierre Sandrin Assignee: Yen Lac Tue
Resolution: Fixed Votes: 0
Labels: VN-Implementation, VN-Testing
Remaining Estimate: 0d
Time Spent: 2d 6.25h
Original Estimate: Not Specified
Environment:

External DAM 1.1.0


Attachments: File api-response.json     PNG File bad-request-error.png     PNG File bynder-image.png     PNG File dam-app-preview-error.png     PNG File freemarker.png     PNG File html.png     PNG File image-2022-01-19-11-24-29-100.png    
Issue Links:
Problem/Incident
documentation
to be documented by EXTDAM-334 DOC: Ext dam 1.1.2 changelog Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Release notes required:
Yes
Date of First Response:
Epic Link: AuthorX Support
Sprint: AuthorX 1
Story Points: 3
Team: AuthorX

 Description   

Steps to reproduce

  1. Setup bynder external DAM with proxyMode enabled
  2. Select an Bynder Asset that contains a | (pipe character)
  3. Generate a link to it in Freemarker
  4. Load the HTML Page

Expected results

The Image should load as other images that do not contain a special character

Actual results

The link to the image returns a 400 Bad Request HTTP error

Workaround

Disable proxyMode (but then it is not possible to get links to the bynder derivates/renditions)

Development notes

The Proxy that is generating links should check for special characters and handle them correctly. I.E. URL-Encode them



 Comments   
Comment by Jesus Alonso [ 19/Jan/22 ]

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