Filename prevents downloading attachment.

Derek White June 24, 2022

When I use the content URL to get an attachment, I get a 404. If I replace the attachment name in the URL with `.../test.ext` it downloads fine.

Is this a bug? Is there a way to validate attachment names for downloading? Should I simply always use a fake name?

Why is the name even included when the unique identifier (id) is there? If I drop the name from the path, it returns "400 - Invalid attachment path". Yet another idiotic endpoint.

0 answers

Suggest an answer

Log in or Sign up to answer