"413 Request Entity Too Large" when serving Angular web (client side) with Nginx

25 views Asked by At

This is my first question ever. Thanks in advance for your help.

I've been working on a web (ANGULAR) whice comunicates with my backend (NODE JS) Everything works fine when serving it with angularCli (ng serve...)

It's deploy time and now i have to put them on different dockers which would be scaled using Amazon EKS service. So following the good practices i moved from serving it with angularCli to nginx

All is working fine except for one service where users have to attach some PDF files. It responds: "413 Request Entity Too Large - nginx"

I understand what that response error means... but my question is why is NGINX cheking/controlling the size of the users requests if angular is running in client side?

I would expect thtat kind of response comming from the NODE JS backend, not the "web serving tool"

Expected behaviour: Browser http request -> NodeJs

is this happening? => Browser http request -> NGINX? -> NodeJS

Does hosting services inform the browsers how much all requests in the served web could be? Or maybe... this response isn't comming from the NGINX inside the web container, but from another NGNIX involved with some AWS.EKS or "whatever infraestructure stuff"?

0

There are 0 answers