En utilisant AWS re:Post, vous acceptez les AWS re:Post Conditions d’utilisation
AWS re:Postre:Post

Load Balancer HTTP 413 Error

0

Solution suggested on Stackoverflow was to increase max http message size.

by creating this file: /.platform/nginx/conf.d/proxy.conf with the content:\nclient_max_body_size 100M;

Where to create this file .. How to do this for an AWS Load Balancer (not Elastic Beanstalk) ?

Sujets
Réseaux et diffusion de contenu
Balises
Elastic Load Balancing
Langue
English
richeso
demandé il y a 2 ans3069 vues
1 réponse
0

It would help a lot if you could describe more about what you're trying to do and what is in your environment. For example what targets are you using for the load balancer (EC2 or Lambda - I assume EC2) and what type of load balancer (I assume Application Load Balancer but that may not be the case). Also: Are you getting an error message? If so, what is it? Is it being generated by the load balancer or the target?

profile pictureAWS
EXPERT
Brettski-AWS
répondu il y a 2 ans
  • richeso
    il y a 2 ans

    Thanks for your post. It was generated from the load balancer side and not the target.

    I finally figured out that the AWS load balancer was just routing traffic to an internal VM where nginx was installed.. so I logged into the VM and changed the nginx configuration in /etc/nginx/nginx.conf to add the line in the http section:

    client_max_body_size 200M;

    then reloaded the new nginx configuration using the command: nginx -s reload ... and the http error 413 no longer appeared.

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.

Instructions pour répondre aux questions

Contenus pertinents