News for hackers. Stuff that matters.
Re:Nginx: a caching, thumbnailing, reverse proxying image se... by m_mueller on Friday February 19, 2016 @02:07AM (#11132089)
Could someone here explain to me how it's possible that a bug like [1] concerning the main functionality of nginx (static file routing) is open since many years, and yet nginx keeps its popularity? Is that really the best we've got?

[1] https://trac.nginx.org/nginx/ticket/97

Re:Nginx: a caching, thumbnailing, reverse proxying image se... by DevOpsTiger on Friday February 19, 2016 @03:47AM (#11132400)
Re:Nginx: a caching, thumbnailing, reverse proxying image se... by m_mueller on Friday February 19, 2016 @04:43AM (#11132569)
So, do I get this right - the bug has been fixed since mid 2015 but the ticket wasn't updated?
Re:Nginx: a caching, thumbnailing, reverse proxying image se... by pcwalton on Friday February 19, 2016 @02:11AM (#11132097)
Probably because every single popular project that has existed for a long time has bugs that have been open for years, so the fact that a bug has been open for years says nothing about the quality of those projects?
Re:Nginx: a caching, thumbnailing, reverse proxying image se... by m_mueller on Friday February 19, 2016 @02:37AM (#11132193)
I disagree. There are bugs and then there are bugs. If a web server messes up static paths and there is no reaction from the maintainers in 4 years other than putting the prio on minor, I have serious trouble trusting the code quality of a project. But so far I haven't really found something that would replace nginx, especially when it comes to serving wsgi apps. Hence my question "is that really the best we got?".