On Wed, Jul 03, 2002 at 12:02:47PM +0200, Oliver Bleutgen wrote:
Simply and boldly offering apache 1.3.26 updates for all distributions would be prone to break a lot of things because of changes like that. It would be hard to get it right again, so everything works still as expected, the configuration files are still valid, and so on.
It's absolutely no question for me that staying with the same version number and backporting security patches is the right thing to do under almost any circumstances. Esp. with apache, where there may be custom modules which depend on that very version.
Just an example --because we talked about exactly this-- which I just read on the httpd list:
I am writing in hopes that you can help us with an urgent problem we are having with a bug fix you put into Apache 1.3.26 I have spent two days tracking this down and am certain the issue is with your fix.
Due to an error in OUR online game code, we were incorrectly requesting files using 'HTTP-1.0' instead of 'HTTP/1.0' on the GET request line. As you know, this is wrong. However, suprisingly, this worked just fine for several years with both Apache and other Web servers, presumably because the server just ignored it or defaulted to HTTP/1.0. If you want to test, try our down-level Apache server at lobby.dqsoft.com with GET /index.html HTTP-1.0 I am sure I am not the only one with this problem, as there are several socket tutorials and such that incorrectly say 'HTTP-1.0'.
q.e.d. Peter -- VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...