Your wisdom on what to do with Apache 2.2 (eol) + mod

RayHunter has asked for the wisdom of the Perl Monks concerning the following question:

Greetings,

I am seeking guidance on what is the righteous path to follow for a system currently running Windows Server 2012 64 bit, Apache 2.2, mod_perl 2.0.8 and Strawberry perl 5.16.3

I realise that forward motion is required, but the momentum to remain stationary is great, so what is wisdom?

I read that mod_perl is really for Apache 2.2. Apache 2.2 is good enough, but it's end of life. We really need mod_perl for speed. I really like Strawberry Perl. Windows is a given. So many paths that lead to disaster.

What to do?

Comment on Your wisdom on what to do with Apache 2.2 (eol) + mod_perl on Windows 64

Replies are listed 'Best First'.
Re: Your wisdom on what to do with Apache 2.2 (eol) + mod_perl on Windows 64 by RonW (Parson) on Dec 09, 2016 at 21:13 UTC
From http://httpd.apache.org/: The Apache HTTP Server Project will only provide maintenance releases of the 2.2.x flavor through June of 2017, and will provide some security patches beyond this date through at least December of 2017. So, you have at least 6 months to prepare for moving to version 2.4.x (or other HTTP server). Also, according to https://perl.apache.org/download/, mod_perl_2.x is supported on Apache HTTP ver 2.4.x. So, looks like you can migrate to Apache 2.4.x and keep using mod_perl 2.x	[reply]
Re: Your wisdom on what to do with Apache 2.2 (eol) + mod_perl on Windows 64 by 1nickt (Canon) on Dec 09, 2016 at 11:21 UTC
Ancient Monastery wisdom: `Quieta non movere` [download] (If it ain't broke don't fix it) The way forward always starts with a minimal test.	[reply] [d/l]
Re: Your wisdom on what to do with Apache 2.2 (eol) + mod_perl on Windows 64 by FreeBeerReekingMonk (Deacon) on Dec 09, 2016 at 22:52 UTC
I got a similar problem. From what I have read, some are installing the new Apache 2.4 and with a redirect rule, redirecting all old perl cgi requests to the old Apache 2.2 server (but at a performance hit, due to an extra server in the chain, but this backserver does not need to serve static files anymore, so it could balance out). This way, when/if mod_perl becomes available, they can switch more easily. Of course, the old Apache only accepts incoming connections from that new Apache, thus, making it less risky (when patches stop, pun intended). edit: Apache began as a-patchy-server (explaining the pun) edit2: Compile ourselves: Yes, Windows world is a bit different (but tell me what to do after the nmake and I'll give it a shot): The houses that offer Apache pre-compiled still do not bundle nor offer it (I checked a few weeks ago, it could be different now). edit3: Or you just jump the gun, hire some temporal staff to help migrate and write a wrapper for your perlscripts to accept mod_proxy_fcgi.	[reply]
Re^2: Your wisdom on what to do with Apache 2.2 (eol) + mod_perl on Windows 64 by RayHunter (Acolyte) on Dec 10, 2016 at 10:55 UTC
Thanks. I also checked, and there were no pre-compiled binaries out there yet, nor hints on using mod_perl on 2.4. Nothing post 2013 in fact. I know it's not broken yet, but when it does break we're going to have a lot to fix We generally don't need all of the functions of mod_perl: just the speed. FastCGI functionality would probably suffice, but as you say, there's the not insignificant cost of porting large existing (10000+ line) code base, and information on running FastCGI/ Apache on windows is also pretty scarce from what I can see. An alternate path is to port to Linux, as support of Linux in corporate hosting has improved. Especially as a VM.	[reply]