HTTP413 Limitations. A technical confirmation needed

Website, Application, Performance
1

What is the name of the domain?

bmsworld.nz

What is the error number?

HTTP413

What is the error message?

Request Entity Too Large

What is the issue you’re encountering

download file serving limitations

What steps have you taken to resolve the issue?

Followed developer console through uploading a file larger than 100MB to the webserver, traced error in dev console

What are the steps to reproduce the issue?

logon to wp-admin and create new file through DownloadManagerPro, use onscreen environment to drag and drop a file into the new file, give it a name, file completes the upload but never completes the last bytes (99.9%) - confirmed error trace in google dev console. 413 request entity too large

2

The nature of my post is as follows;
I have just finished setting up a new webserver in my homelab - it needs to send larger files 1mb to 10gb, intent is for single origin file hosting, no need to ‘’‘edge’’ host these files.
web server is not intended for raw speed, but responsiveness and stability [finances only allow for this]

Is there a solution to this 413 entity too large? Can i route these file transactions direct from home without going through CF? I cannot not have the beautiful SSL solutions ande zero trust tunnels.

With all this in mind, what would you do?

3

I feel that somehow this post might not belong here as I think the only way forward is through some smart dns or routing hackery on my end

4

This topic was automatically closed after 15 days. New replies are no longer allowed.