You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's a single bug. Do not report multiple bugs in one issue.
It's a frontend issue, not a backend issue; Otherwise please create an issue on the backend repo instead.
Summary
When creating a post with an image that is larger than the max client_max_body_size, the UI does not handle the http response "413 Request entity too large".
Since the request never reaches the backend, only the UI can handle it correctly.
The error displayed by the front end is a JSON parsing error since it might be the default error handling.
Steps to Reproduce
Setup the instance with default settings
Create a post in any community with a picture larger than 1MB (default limit)
Notice the error popup in the bottom left of the screen
Changing the nginx client_max_body does not fix the underlying issue but can be set to a higher limit to mitigate this issue.
Technical Details
Return of the upload is:
<html><head><title>413 Request Entity Too Large</title></head><body><center><h1>413 Request Entity Too Large</h1></center><hr><center>nginx</center></body></html>
Requirements
Summary
When creating a post with an image that is larger than the max client_max_body_size, the UI does not handle the http response "413 Request entity too large".
Since the request never reaches the backend, only the UI can handle it correctly.
The error displayed by the front end is a JSON parsing error since it might be the default error handling.
Steps to Reproduce
Changing the nginx client_max_body does not fix the underlying issue but can be set to a higher limit to mitigate this issue.
Technical Details
Return of the upload is:
http status is 413
Lemmy Instance Version
0.18
Lemmy Instance URL
https://jlai.lu
The text was updated successfully, but these errors were encountered: