It's not a misconfiguration, is a huge bug. A wasted two days of sleep for something that is 100% a bug. Please read here: https://laracasts.com/discuss/channels/general-discussion/homestead-nginx-serving-wrong-images-and-only-cut-in-the-middle He mentions the same exact problem and also he points to https://tech.blog.aknin.name/2011/11/04/nginxgzip-module-might-silently-corrupt-data-upon-backend-failure/ where the author says that Niginx will not fix it. So he already tried he was rebuffed.
On Wed, Feb 22, 2023 at 2:32 PM Sergey A. Osokin <o...@freebsd.org.ru> wrote: > On Wed, Feb 22, 2023 at 02:05:21PM -0500, Saint Michael wrote: > > I wonder if Nginx will ever fix this issue. It's a clear bug in the > > product. I wasted two days of sleep on this issue. > > From your previous email you've reported you've found a solution, so > that seems like not a bug and probably a misconfiguration on your > side or misunderstading of the official documentation. > > However, in case you want to fill that as a bug, please use the > following URL, [1] , to submit a bug report with full descrpition > of your case. > > Thank you. > > 1. https://trac.nginx.org/nginx/ > > -- > Sergey A. Osokin > _______________________________________________ > nginx mailing list > nginx@nginx.org > https://mailman.nginx.org/mailman/listinfo/nginx >
_______________________________________________ nginx mailing list nginx@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx
