🚀 go-pugleaf

In article <9qn26c$1094$1@machaut.medieval.org>,
Todd Michel McComb <mccomb@medieval.org> wrote:
>In article <9qm1qn$1db2$1@nntp1.ba.best.com>, Joe Smith <inwap@best.com> wrote:
>>That's because these two lines in .bhtaccess got translated to
>>three lines in .htaccess:
>
>You're kidding me... they're editing our files?  That is absolutely
>outrageous.

It is an automatic process that converts BESTWWWD-specific SSI directives
to Apache style directives.  It would be unforgivable if my web site
stopped working because they did NOT do any conversion.

>If I had anything left on Best, I would be seriously pissed.

The old file is renamed to "index.shtml-before-migration" by the process
that translates "index.shtml".  Here is a diff:

60c60
< (<!--#include file="u/sally/macleod.count"--> hits)<br>
---
> (<!--#include virtual="u/sally/macleod.count"--> hits)<br>
70c70
< <li>This is the <!--#counter file="index.count"-->
< <A HREF="web-hints/count-list.html">hit</A> on this top-level index.
---
> <li>This is the <!--#set var="COUNTER_INFO" value="${SCRIPT_FILENAME}" -->
> <!--#include virtual="/cgi-bin/count-ssi.cgi?-findex.count"-->
> <A HREF="web-hints/count-list.html">hit</A> on this top-level index.

>There is no possible way I have granted or implied any
>sort of permission to modify my web files.  No way.

There is an implied agreement that Server Side Includes that worked with
the old web server (BESTWWWD) will continue to work on the new platform
(Apache).  This is what the majority of users would want: no effort on
my part, just make sure that my site works.
	-Joe

--
See http://www.inwap.com/ for PDP-10 and "ReBoot" pages.