aws / aws/aws-eb-python-dockerfiles

Missing buffer size option for wsgi lead to 502

Offen
#4 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Shell
Sterne
61
Forks
33
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

When deploying a Flask app to EBS (using the [tutorial](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create-deploy-python-flask.html)) one can face 502 HTTP status code when returning response with a size bigger than 4096.
```
invalid request block size: 4654 (max 4096)...skip
```

Apparently this script does not contemplate to configure the buffer-size option for WSGI.
After reading the doc about [configuration on EBS](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create-deploy-python-container.html#create-deploy-python-custom-container-envprop) I am not sure if I can specify such an option without doing a hacky replace of the `uwsgi-start.sh` script and rerun it.

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Start by reading the uwsgi-start.sh script and the linked Elastic Beanstalk Python container configuration documentation. Reproduce the 502 with a response larger than 4096 and trace how WSGI options are passed. Done means the buffer-size option can be configured through the supported EBS setup without replacing the script.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
aws, flask, python, shell
Bereich
backend, cloud
Issue-Typ
Feature
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
42/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.