Apache version

[fiberadm]

My Sonic-hosted site gives a response header of:
Server: Apache/1.3.41 (Unix) mod_auth_pam/1.1.1 FrontPage/5.0.2.2635 PHP/4.4.9

The Apache website says 1.3 is "no longer maintained" .

Are there Sonic servers running Apache 2.x ?
Are there plans to migrate from 1.3 to 2.x ?

[kgc]

Our customer web cluster runs a locally maintained and patched version of Apache. We've ported all of our local modifications that would be required to move to Apache 2 but have run into some performance issues that we've been unable to resolve that currently block us from moving forward to replace the older servers. This isn't a priority for us at this time.

[jhudgins]

It's been nearly a year since the last post here, and I'm curious as to whether the situation WRT an Apache upgrade has changed. I've been migrating Drupal sites to Sonic hosting from my own servers, and have run into a couple of .htaccess syntax problems due to the old version of Apache currently in use at Sonic.

[joemuller]

Could you provide an example of which htaccess functions aren't behaving as expected?

[jhudgins]

Sure. One is the lack of cookie-generation support in Apache 1.3; for example:

Code: Select all

RewriteRule .* - [CO=mt_device:desktop:.example.com:1440:/]

Another which cropped up recently is part of the standard Drupal 7.22 .htaccess file. This expression triggers an error in Apache 1, but not Apache 2:

Code: Select all

<FilesMatch "\.(engine|inc|info|install|make|module|profile|test|po|sh|.*sql|theme|tpl(\.php)?|xtmpl)(|~|\.sw[op]|\.bak|\.orig|\.save)?$|^(\..*|Entries.*|Repository|Root|Tag|Template)$|^#.*#$|\.php(~|\.sw[op]|\.bak|\.orig\.save)$">

There's a syntax error in there, I think (a leading | operator), but the different regular expression parser in Apache 2 tolerates it. It'll be patched soon, and is easy enough to fix. As Apache 1.3 ages, however, I anticipate more things like this, so I'm curious about whether an update is in the cards for the Sonic hosting cluster.