{"id":35,"date":"2003-08-26T07:15:08","date_gmt":"2003-08-26T11:15:08","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/rlucastemp\/2003\/08\/26\/downgrading-to-apache-13-from-apac"},"modified":"2003-08-26T07:15:08","modified_gmt":"2003-08-26T11:15:08","slug":"downgrading-to-apache-13-from-apache-2-under-red-hat-9","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/rlucastemp\/2003\/08\/26\/downgrading-to-apache-13-from-apache-2-under-red-hat-9\/","title":{"rendered":"Downgrading to Apache 1.3 from Apache 2 under Red Hat 9"},"content":{"rendered":"

<\/a><\/p>\n

Apache 2.0 can be a real cast-iron bitch.  It’s got this cool
\nsupport for threading that you think will make your life easier but it
\nturns out to have all sorts of little API differences that break your
\nlegacy apps, in really horrifyingly difficult to discern ways. 
\nThis might be the apps’ fault or Apache’s fault, but either way it
\nmakes your life hard if you are used to things working smoothly under
\nApache 1.3x and then get jolted into the cruel world of 2.x.<\/p>\n

 <\/p>\n

Red Hat has put out Apache 2.0 since at least Red Hat 8.0.  Red
\nHat 9 comes with Apache 2 as well.  However, Red Hat knows about
\nthe problems as well as anybody: the non-gratis Red Hat Enterprise
\nLinux distros come with Apache 1.3x!  [UPDATE: Enterprise
\nLinux 2.x came with 1.3.x; Red Hat has made
\nthe questionable choice of putting Apache 2 in Enterprise Linux
\n3.0 and removing<\/em> things like the venerable Pine…] 
\nIt’s clear that if you actually want stability, you should use 1.3
\nuntil the rest of the world catches up with Apache 2.0.<\/p>\n

(Other people know this too: see http:\/\/linux.derkeiler.com\/Mailing-Lists\/RedHat\/2003-07\/0726.html<\/a> and http:\/\/lists.freshrpms.net\/pipermail\/rpm-list\/2003-May\/004682.html<\/a> )<\/p>\n

If you want to downgrade your Red Hat 9 Apache version, you can
\neither try to compile, which is fairly straightforward once you find
\nthe fixes I mention below, but if you want mod_perl and mod_ssl, and if
\nyou are not very smart, like me, you really are better off using the
\nrpm packaged versions.<\/p>\n

 <\/p>\n

Unfortunately, the openssl 9.7 that comes with Red Hat 9 will
\nprevent you from installing mod_ssl 2.8 to go with Apache 1.3. 
\nSo, here’s how to install Apache 1.3 with mod_perl and mod_ssl:<\/p>\n

 <\/p>\n

1. Erase the apache 2.0 rpm from the system.  Nuke the dependent packages as well (mod perl, mod ssl, php, etc).<\/p>\n

2. Get:<\/p>\n

apache-1.3.27-2.i386.rpm<\/p>\n

mod_perl-1.26-5.i386.rpm<\/p>\n

mod_ssl-2.8.12-2.i386.rpm<\/p>\n

openssl-0.9.6b-32.7.i386.rpm<\/p>\n

 Warning: these packages are
\nend-of-lifed and may present security hazards (read: your box could be
\nowned if you do this!).  I am no longer running a box with these
\npackages and I suggest you do not either!  I currently recommend
\napachetoolbox (apachetoolbox.com) for a quick and relatively painless
\nrecompile, rather than relying upon these old dusty rpms.
\n<\/span><\/p>\n

3. Install apache and mod_perl.  Ensure that it works fine (sanity check).<\/p>\n

4. Back up \/usr\/share\/ssl\/* to e.g. \/usr\/share\/ssl9.7a\/<\/p>\n

5. Back up \/usr\/bin\/openssl to e.g. \/usr\/bin\/openssl9.7a<\/p>\n

6. Install openssl with a suitable command line:<\/p>\n

rpm -ivh openssl-0.9.6b-32.7.i386.rpm –excludedocs –oldpackage –force<\/p>\n

7. Now back up \/usr\/share\/ssl\/* to \/usr\/share\/ssl9.6b\/ and restore ssl9.7a\/<\/p>\n

8. Back up \/usr\/bin\/openssl to openssl9.6b and restore openssl9.7a<\/p>\n

9. You should now have both openssl 9.6b and 9.7a installed on your system.  You can verify this with rpm -q openssl<\/p>\n

10. Now install the mod_ssl RPM.<\/p>\n

 <\/p>\n

Make sure you’ve used lokkit (or manually arranged) to open up both
\nport 80 and 443 or else you’ll drive yourself crazy for 20 minutes,
\nlike I did, wondering why http is running but not answering.<\/p>\n","protected":false},"excerpt":{"rendered":"

Apache 2.0 can be a real cast-iron bitch.  It’s got this cool support for threading that you think will make your life easier but it turns out to have all sorts of little API differences that break your legacy apps, in really horrifyingly difficult to discern ways.  This might be the apps’ fault or Apache’s […]<\/p>\n","protected":false},"author":1180,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1460],"tags":[],"class_list":["post-35","post","type-post","status-publish","format-standard","hentry","category-rlucasstories"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/rlucastemp\/wp-json\/wp\/v2\/posts\/35","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/rlucastemp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/rlucastemp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/rlucastemp\/wp-json\/wp\/v2\/users\/1180"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/rlucastemp\/wp-json\/wp\/v2\/comments?post=35"}],"version-history":[{"count":0,"href":"https:\/\/archive.blogs.harvard.edu\/rlucastemp\/wp-json\/wp\/v2\/posts\/35\/revisions"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/rlucastemp\/wp-json\/wp\/v2\/media?parent=35"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/rlucastemp\/wp-json\/wp\/v2\/categories?post=35"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/rlucastemp\/wp-json\/wp\/v2\/tags?post=35"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}