Even the server app itself does not know it’s file size limit most of the time.
The fuck are you talking about? It’s likely an ENV variable or config variable that literally HAS to be accessible to any file upload in order to even return this error message. Quit making shit up.
Server (application) does not know the site upload limit because it was set by reverse proxy. Any of them could reply with http 413 status and client will just show you the message like screenshot.
The fuck are you talking about? It’s likely an ENV variable or config variable that literally HAS to be accessible to any file upload in order to even return this error message. Quit making shit up.
Here is the faq related to what I am talking about.
https://www.cyberciti.biz/faq/linux-unix-bsd-nginx-413-request-entity-too-large/
Server (application) does not know the site upload limit because it was set by reverse proxy. Any of them could reply with http 413 status and client will just show you the message like screenshot.