413 Entity too large - Pro plan
I'm on the pro plan which is 100MB upload limit and I'm uploading a file that's 200MB BUT I'm getting that 413 error. My request is GZIP'd and the file size is around 10MB on the receiving end (based off size tests locally).
Why am I getting this error if the request is not 200MB as it's GZIP'd?
3 Replies
What's the content-length? Do you mean your recieving end gzips it after, or it's pre-compressed by the client?
File size is 200MB JSON, gzipped is around 12MB. I'm basically sending a POST request to our Web API which is behind Cloudflare but I receive that error.
After tests outside of Cloudflare it appears your upload limit of 100MB for the pro plan is the issue. I'm just curious as too why Cloudflare is going off the original 200MB size instead of the gzipped size. I arrived GZIPPed too as I'm already uploading files of around 50MB and they arrive instantly at around 4-5MB.
for clarification: I'm not a Cloudflare employee
Cloudflare doesn't care what the uncompressed size is, only the content-length and actual size of the payload. It's really easy to test this, I took an uncompressed file of ~136mb and gzipped it down to ~64mb and it uploaded fine, original failed on a zone with an upload limit of 100 MB.
What's the exact request/response uploads? Specifically looking for content-length on the upload and if cf-cache-status exists on the response