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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.