Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify that the async upload endpoint will return 404 in some cases #1983

Merged
merged 1 commit into from
Nov 6, 2024
Merged

Clarify that the async upload endpoint will return 404 in some cases #1983

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelogs/client_server/newsfragments/1983.clarification
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Clarify that the async upload endpoint will return 404 in some cases.
19 changes: 19 additions & 0 deletions data/api/client-server/content-repo.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,6 +126,25 @@ paths:
"errcode": "M_FORBIDDEN",
"error": "Cannot upload this content"
}
"404":
description: |-
The user has provided an invalid MXC ID. Some reasons for this error include:

- The MXC ID was not created with [POST /_matrix/media/v1/create](/client-server-api/#post_matrixmediav1create).
- The MXC ID has expired.

A [standard error response](/client-server-api/#standard-error-response)
will be returned with the `errcode` `M_NOT_FOUND`.
content:
application/json:
schema:
$ref: definitions/errors/error.yaml
examples:
response:
value: {
"errcode": "M_NOT_FOUND",
"error": "Unknown media ID"
}
"409":
description: |-
The endpoint was called with a media ID that already has content. A
Expand Down