You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 31, 2020. It is now read-only.
In it's current form, the attachment endpoint only takes an entity and a digest as parameters. This means it just references a file and not a specific post having that file as attachment. The problem this creates is that different posts can reference the same attachment with different content-type, in such situation: what Content-Type should the attachment endpoint return?
From what I've been told, the current rule would be to return the Content-Type of the most recent post. But this is problematic: what if two apps use the same file with different content-type. The app that created the post first would now receive the wrong headers when retrieving files from the attachment endpoint.
The text was updated successfully, but these errors were encountered:
In it's current form, the
attachment
endpoint only takes anentity
and adigest
as parameters. This means it just references a file and not a specific post having that file as attachment. The problem this creates is that different posts can reference the same attachment with differentcontent-type
, in such situation: whatContent-Type
should theattachment
endpoint return?From what I've been told, the current rule would be to return the
Content-Type
of the most recent post. But this is problematic: what if two apps use the same file with differentcontent-type
. The app that created the post first would now receive the wrong headers when retrieving files from theattachment
endpoint.The text was updated successfully, but these errors were encountered: