🚀 go-pugleaf

In article <3BB4D6F8.B3795CDE@best.com>, avm  <avm@best.com> wrote:
>I'm in the middle of the migration as well, here's a few thoughts.
>It looks like the team responsible for migrating have put a fair amount of
>thought into it, and the fact that they have moved the files over themselves
>is appreciated, and anyone who's time is limited will probably agree. Most
>things seem to be working in my new ENV but there's a few niggles.
>The old bestwwwd uses REMOTE_HOST env var, this does not exist on this version
>of apache, which uses REMOTE_ADDR, also could someone clarify what this
>version of apache is, i find this explanation from SERVER_SOFTWARE confusing,
>especially with referance to 'front page'.

The REMOTE_HOST functionality can be enabled with "HostnameLookups
on", perhaps in your .htaccess file (not 100% on that), or by adding
some sort of <Limit ...> that either allows from or denys from a
hostname (rather than an IP).

Note that in the default CustomLog setup, this will cause the logs
to be written out using the value in REMOTE_HOST rather than
REMOTE_ADDR, which is probably not very useful. (If the DNS was
bogus, it's hard to track that down after the logs are run.)

>SERVER_SOFTWARE = mod_jk FrontPage/4.0.4.3 Confluence Apache/1.3.19
>Ben-SSL/1.42 (Unix)
>
>Is this related to the Virtual hosting set up?

Yep. mod_jk is a Java servlet module. I'm not sure what Confluence is.

>Also there are some custom ENVs like RESELLER, OPBACCOUNTID and OPBSITEID
>which i asume the admins are using for account auditing purposes. Harvesting
>user data or some such.

Those are probably coming from whatever Confluence is. I'd bet it's
actually for your use rather than the sysadmins. Maybe some sort of
shopping cart-type thing.

>One other thing i notice is that we don't have the latest and greatest version
>of perl on this new machine. Why is that ? I'm sure perl 5.6 would be
>appreciated.

This would complicate the migration project 10- or 20-fold. It'd force the
new perl onto people as they migrate over, and when their sites don't work
because of something the perl team decided to break, they'll blame Verio.

- dpk