3 ms·
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
by m_mueller 11y ago
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 https://trac.nginx.org/nginx/ticket/97
- pcwalton 11y agoProbably 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?
- m_mueller 11y agoI 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?".
- DevOpsTiger 11y agohttps://trac.nginx.org/nginx/changeset/2797b4347a2af4e8fd46dc5d1def5083813f38f1/nginx https://trac.nginx.org/nginx/changeset/2797b4347a2af4e8fd46d...
- m_mueller 11y agoSo, do I get this right - the bug has been fixed since mid 2015 but the ticket wasn't updated?