Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uploading overlarge profile image results in bad gateway Apache error for the client... #1198

Open
mikesname opened this issue Aug 30, 2019 · 2 comments · Fixed by #1229
Open
Labels

Comments

@mikesname
Copy link
Contributor

Bad Gateway
The proxy server received an invalid response from an upstream server.

This should be handled gracefully by Play. On the backend we have an Akka streams exception:

Tearing down FileSink(/tmp/playtemp7370616944964610281/multipartBody2184519533985252596asTemporaryFile) due to upstream error
@mikesname mikesname added the bug label Aug 30, 2019
@mikesname
Copy link
Contributor Author

mikesname commented Jan 16, 2020

~Still investingating: possibly related to this bug: https://bz.apache.org/bugzilla/show_bug.cgi?id=60330
~

Now (circa 2.8) no error on the Play end, which seems to be handling max content correctly and returning 413. Apache is accepting the whole file upload and then erroring, however. The mystery deepens.

mikesname added a commit to mikesname/ehri-frontend that referenced this issue Jan 16, 2020
 - define max size in MB and read config to bytes
 - add logging
 - fix typo in text error string

No luck attempting to resolve EHRI#1198 though.
mikesname added a commit to mikesname/ehri-frontend that referenced this issue Jan 16, 2020
 - define max size in MB and read config to bytes
 - add logging
 - fix typo in text error string

No luck attempting to resolve EHRI#1198 though.
@mikesname mikesname reopened this Jan 17, 2020
@mikesname
Copy link
Contributor Author

Latest update: still seeing an error. Have tested on Apache 2.4.52 and Nginx on Ubuntu 22.04 and unable to reproduce error. Have also updated Apache on the server to 2.4.54 and error still occurs. Haven't yet tested Nginx on the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant