Skip to content

minidump endpoint does not respond 413 for too large content #5838

@jpnurmi

Description

@jpnurmi

While changing the Native SDK to handle HTTP 413 Content Too Large (NATIVE-160), we found out that unlike /envelope/, the /minidump/ endpoint doesn't respond with 413 but with 400 + reason in the body:

[ERROR http_transport_mac.mm:259] HTTP status 400, response = "{"detail":"invalid multipart data","causes":["stream size exceeded limit: 209715200 bytes"]}"

Is it possible to make the minidump endpoint respond 413? Not sure if this is intentional or a miss, but I thought I'd open a ticket and see where it takes us. :)

_Originally posted by @jpnurmi in getsentry/sentry-native#1647 (comment)

Metadata

Metadata

Assignees

Labels

bugSomething isn't working
No fields configured for issues without a type.

Projects

Status
No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions