Sentry responded with an error: HTTP 413: Request Entity Too Large

I have an exception being raised in a POST request handler in Tornado. When that exception is sent to Sentry via self.captureException(True), I am seeing:

ERROR:sentry.errors:Sentry responded with an error: HTTP 413: Request Entity Too Large (url: https://sentry.io/api/148507/store/)
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/raven/contrib/tornado/__init__.py", line 70, in _handle_result
    future.result()
  File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py", line 237, in result
    raise_exc_info(self._exc_info)
  File "<string>", line 3, in raise_exc_info
HTTPError: HTTP 413: Request Entity Too Large

In the POST body is a large file. I tried to exclude the POST body data by adding the 'raven.processors.RemovePostDataProcessor', but I am still getting the 413 response.

app.sentry_client = AsyncSentryClient(_sentry_dsn, 
	processors=(
		'raven.processors.SanitizePasswordsProcessor',
		'raven.processors.RemovePostDataProcessor'
	)
)

I am using raven==6.0.0.

[sergei-maertens]

I’ve also just run into this, looks like breadcrumbs are causing 413s. Sentry itself is self-hosted, and we’re using Django integration.

However, it looks like there’s no setting to disable breadcrumbs in a Django context, or am I looking at the wrong place?

[ashwoods]

Closed as duplicate #604