Request Entity Too Large
See original GitHub issueRecently started getting the follow error, without any explicit change to Raven or Sentry configuration. Google results are unrevealing. Is there something known that can cause this?
Any proper ways of logging more fully the original AttributeError
, which caused the Sentry error, besides disabling Sentry?
INFO:werkzeug:172.17.42.1 - - [29/Apr/2015 01:02:51] "POST / HTTP/1.1" 500 -
ERROR:sentry.errors:Unable to reach Sentry log server: HTTP Error 413: Request Entity Too Large (url: https://app.getsentry.com/api/39671/store/, body: b'<html>\r\n<head><title>413 Request Entity Too Large</title></head>\r\n<body bgcolor="white">\r\n<center><h1>413 Request Entity Too Large</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n')
Traceback (most recent call last):
File "/usr/local/lib/python3.4/site-packages/raven/transport/threaded.py", line 159, in send_sync
super(ThreadedHTTPTransport, self).send(data, headers)
File "/usr/local/lib/python3.4/site-packages/raven/transport/http.py", line 49, in send
ca_certs=self.ca_certs,
File "/usr/local/lib/python3.4/site-packages/raven/utils/http.py", line 62, in urlopen
return opener.open(url, data, timeout)
File "/usr/local/lib/python3.4/urllib/request.py", line 461, in open
response = meth(req, response)
File "/usr/local/lib/python3.4/urllib/request.py", line 571, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/local/lib/python3.4/urllib/request.py", line 499, in error
return self._call_chain(*args)
File "/usr/local/lib/python3.4/urllib/request.py", line 433, in _call_chain
result = func(*args)
File "/usr/local/lib/python3.4/urllib/request.py", line 579, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 413: Request Entity Too Large
ERROR:sentry.errors:Failed to submit message: "AttributeError: 'dict' object has no attribute 'encode'"
Issue Analytics
- State:
- Created 8 years ago
- Reactions:3
- Comments:50 (25 by maintainers)
Top Results From Across the Web
How to Solve the "413 Request Entity Too Large" Error - Kinsta
In a nutshell, the “413 Request Entity Too Large” error is a size issue. It happens when a client makes a request that's...
Read more >Fixing 413 Request Entity Too Large Errors - KeyCDN Support
A 413 Request Entity Too Large error occurs when a request made from a client is too large to be processed by the...
Read more >Why am I receiving a (413) Request Entity Too Large when ...
Answer: A 413 request entity too large error occurs when a request made from a client is too large to be processed by...
Read more >How to avoid Request Entity Too Large 413 error
This directive defines the maximum amount of data Nginx will accept in an HTTP request. By default this value is set to 1...
Read more >413 Request Entity Too Large - Microsoft Q&A
Hi @nutntion-5142,. IIS has a limit for the size of the files users can upload to an application. If the file size exceeds...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m going to take a look at this.
I am still experiencing this issue even after updating to version 6.10.0.