Carl Brewer wrote: > Torsten Foertsch wrote: >> On Wed 28 Jan 2009, Issac Goldstand wrote: >> The only thing that confuses me is the version string "2.7.0" while >> the TAR file is named 2.11. > > If I can hijack this for a second ... where does the mod_apreq2 string > get set? I'm trying to trace a segfault problem on a CentOS 5.2 box and > while I think I have libapreq2.08 running, the version returned is : > > Server: Apache/2.2.11 (Unix) mod_ssl/2.2.11 OpenSSL/0.9.8b > mod_apreq2-20051231/2.6.0 mod_perl/2.0.4 Perl/v5.8.8 > > That doesn't look right to me on a box with libapreq 2.08 compiled on > the 30th of Dec 2008!
I'm not sure of the 2.7.0 - I *think* it means it's the 7th release of the 2.x version (which is not the same as the version number). I wasn't the one who set that up, though, so I won't comment. The date is the date the code was released, not compiled.
