Apache upgrade - GoFuckYourself.com

Tipsy · 08-15-2002, 07:21 AM

Anybody know of any good (and easy to understand) documentation for upgrading apache from 1.3 to 2.x?

buran · 08-15-2002, 07:24 AM

http://httpd.apache.org/docs-2.0/upgrading.html

Although it's important to note that 2.x is still pre-beta, and not safe for running in a production environment.

Tipsy · 08-15-2002, 07:26 AM

Thanks for the link. Apache seems to suggest that 2.x is now post beta but maybe I misread it. However, there is a nasty little worm floating around that hits version below 2.x.

foe · 08-15-2002, 07:32 AM

dont upgrade yet. wait till it gets out of beta

Tipsy · 08-15-2002, 07:32 AM

One quick question though which is why I was after an 'idiots guide' is I presume once upgraded php etc have gotta be rejiggered to work with the newer version?

salsbury · 08-15-2002, 09:06 AM

why upgrade when there's no need? there aren't really any new features that are significant.

plus, PHP is not yet marked as "release" with Apache 2.x. PHP kinda sucks - ok more than kinda - but a lot of people want it to work, so upgrading now would probably not be wise if you need PHP.

i'd stick with 1.3.26. it's fast, it works great, it's compatible.

Tipsy · 08-15-2002, 11:02 AM

I was looking at it purely because of the worm out there. Instead I'll do something I should have done a while ago and try some virus protection on the server.

Lane · 08-15-2002, 11:09 AM

its been tested for almost 2 years

should be stable enough

fiveyes · 08-15-2002, 11:30 AM

Quote:

Originally posted by buran
http://httpd.apache.org/docs-2.0/upgrading.html

Although it's important to note that 2.x is still pre-beta, and not safe for running in a production environment.

Not so. Though the 1.3 version is still supported, "Apache 2.0.40 is the best available version" and has been General Availability (GA) for quite some time. The GA designation means that the release is past alpha, is past beta and is recommended for production usage.

The only caveat that applies is that the modules for 1.3 are incompatible with 2.0 and not all of them have been upgraded to the new Apache API. Even then, there only remains some obscure, infrequently required modules to be rewritten. Most all of the common ones are available and working.

Tipsy · 08-15-2002, 11:33 AM

Quote:

Originally posted by fiveyes

Not so. Though the 1.3 version is still supported, "Apache 2.0.40 is the best available version" and has been General Availability (GA) for quite some time. The GA designation means that the release is past alpha, is past beta and is recommended for production usage.

The only caveat that applies is that the modules for 1.3 are incompatible with 2.0 and not all of them have been upgraded to the new Apache API. Even then, there only remains some obscure, infrequently required modules to be rewritten. Most all of the common ones are available and working.

Thanks - from looking at the site it seemed well out of beta. Still gonna be a pain in the ass to upgrade though

08-15-2002, 07:21 AM	#1
Tipsy Confirmed User Join Date: Jul 2001 Location: See sig Posts: 6,989	Apache upgrade Anybody know of any good (and easy to understand) documentation for upgrading apache from 1.3 to 2.x? __________________ Ignorance is never bliss.

08-15-2002, 07:24 AM	#2
buran Confirmed User Join Date: Mar 2002 Location: how'd I get here? Posts: 264	http://httpd.apache.org/docs-2.0/upgrading.html Although it's important to note that 2.x is still pre-beta, and not safe for running in a production environment. __________________ [this signature intentionally left blank]

08-15-2002, 07:26 AM	#3
Tipsy Confirmed User Join Date: Jul 2001 Location: See sig Posts: 6,989	Thanks for the link. Apache seems to suggest that 2.x is now post beta but maybe I misread it. However, there is a nasty little worm floating around that hits version below 2.x. __________________ Ignorance is never bliss.

08-15-2002, 07:32 AM	#5
Tipsy Confirmed User Join Date: Jul 2001 Location: See sig Posts: 6,989	One quick question though which is why I was after an 'idiots guide' is I presume once upgraded php etc have gotta be rejiggered to work with the newer version? __________________ Ignorance is never bliss.

08-15-2002, 09:06 AM	#6
salsbury Confirmed User Join Date: Feb 2002 Location: Seattle Posts: 1,070	why upgrade when there's no need? there aren't really any new features that are significant. plus, PHP is not yet marked as "release" with Apache 2.x. PHP kinda sucks - ok more than kinda - but a lot of people want it to work, so upgrading now would probably not be wise if you need PHP. i'd stick with 1.3.26. it's fast, it works great, it's compatible. __________________

08-15-2002, 07:32 AM	#4
foe Confirmed User Join Date: May 2002 Location: CT Posts: 5,246	dont upgrade yet. wait till it gets out of beta

08-15-2002, 11:02 AM	#7
Tipsy Confirmed User Join Date: Jul 2001 Location: See sig Posts: 6,989	I was looking at it purely because of the worm out there. Instead I'll do something I should have done a while ago and try some virus protection on the server. __________________ Ignorance is never bliss.

08-15-2002, 11:09 AM	#8
Lane Will code for food... Join Date: Apr 2001 Location: Buckeye, AZ Posts: 8,496	its been tested for almost 2 years should be stable enough __________________