Mailing List Archive

two undocumented incompatibilities between 0.8.14 and 0.6.? (fwd)
I'll ack this later

Forwarded message:
> From reinpost@win.tue.nl Wed Nov 15 13:35:18 1995
> Date: Wed, 15 Nov 1995 21:34:58 GMT
> Message-Id: <199511152134.VAA20042@wsinis02.win.tue.nl>
> To: apache-bugs@apache.org
> X-URL: mailto:apache-bugs@apache.org
> X-Mailer: Lynx, Version 2.4-FM
> X-Personal_name: Reinier Post
> From: webmaster@win.tue.nl
> Subject: two undocumented incompatibilities between 0.8.14 and 0.6.?
>
> > Compatibility Notes with NCSA's Server
>
> Dear Apache,
>
> Some time ago, we replaced our NCSA 1.3 (running at http://www.win.tue.nl:82/
> as a backup for the main server) with Apache 0.6.5.
>
> No problems were found at the time. The configuration files weren't changed.
> We are still using an OldScriptAlias for one of our services.
==============
>
> The new 0.8.14 suddenly complains about this directive. Could you document
> this change, please?
>
> A second problem is that we're getting more slashes in our URLs than we used to.
> Redirections I haven't asked for are automatically being sent by the server.
> Again, 0.6.5 didn't have this problem.
>
> In srm/CHANGES there are some on hints on why this could be caused;
> I'll investigate the problem in detail if you want me to. Please mention
> this in your compatibility list, for it is very annoying. (Lots of URLs
> no longer work and I don't know how to fix it reliably.)
>
> Thanks. Great server, incidentally.
>
> Reinier Post webmaster@win.tue.nl
>
Re: two undocumented incompatibilities between 0.8.14 and 0.6.? (fwd) [ In reply to ]
> > No problems were found at the time. The configuration files weren't changed.
> > We are still using an OldScriptAlias for one of our services.
> ==============

Interesting - this is something that came in with NCSA's httpd 1.0, and
its format isn't documented anywhere, and you're the first to complain
:) I'll add it to the online docs saying it was removed, though I don't
know if we'll support it (and for the 1.0 concious developers, I'm not
calling it showstopping! :)

> > A second problem is that we're getting more slashes in our URLs than we used to.
> > Redirections I haven't asked for are automatically being sent by the server.
> > Again, 0.6.5 didn't have this problem.
> >
> > In srm/CHANGES there are some on hints on why this could be caused;
> > I'll investigate the problem in detail if you want me to. Please mention
> > this in your compatibility list, for it is very annoying. (Lots of URLs
> > no longer work and I don't know how to fix it reliably.)

There have indeed been a *lot* of changes, mostly because this is very
subtle stuff and NCSA's httpd had quite a few, er, implementation quirks
that made developing a solid model for translating URL's to file
resources rather difficult. The best we can say is try 0.8.16, if that
doesn't work we have some patches we can give you for some /-related
problems, if that doesn't work give me some examples and I'll help track
it down.

Brian


--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@organic.com brian@hyperreal.com http://www.[hyperreal,organic].com/
Re: two undocumented incompatibilities between 0.8.14 and 0.6.? (fwd) [ In reply to ]
Brian wrote...

> > > No problems were found at the time. The configuration files weren't changed.
> > > We are still using an OldScriptAlias for one of our services.
> > ==============
>
> Interesting - this is something that came in with NCSA's httpd 1.0, and
> its format isn't documented anywhere, and you're the first to complain
> :)

I think I brought this up once. A friend of mine here has an ancient
httpd setup which used this. He realised it was better to upgrade his
setup than try to get Apache to play dumb.

> > > In srm/CHANGES there are some on hints on why this could be caused;
> > > I'll investigate the problem in detail if you want me to. Please mention
> > > this in your compatibility list, for it is very annoying. (Lots of URLs
> > > no longer work and I don't know how to fix it reliably.)
>
> There have indeed been a *lot* of changes, mostly because this is very
> subtle stuff and NCSA's httpd had quite a few, er, implementation quirks
> that made developing a solid model for translating URL's to file
> resources rather difficult. The best we can say is try 0.8.16, if that
> doesn't work we have some patches we can give you for some /-related
> problems, if that doesn't work give me some examples and I'll help track
> it down.

I've been dealing (or at least trying to) with this user in the bugs
mail. I'm pretty sure he's accidentally abusing the use of Alias to work
like DocumentRoot as well as try to get Apache to understand CERN-like
config settings.

I don't think there's anything we need to do to Apache apart from
try to document how CERN users should switch.. and for that we need a
CERN user to write the docs.

rob
Re: two undocumented incompatibilities between 0.8.14 and 0.6.? (fwd) [ In reply to ]
> > We are still using an OldScriptAlias for one of our services.
> ==============

Interesting - this is something that came in with NCSA's httpd 1.0, and
its format isn't documented anywhere, and you're the first to complain

OldScriptAlias is back-compatibility support for a pre-CGI scripting
interface which was the only way to run scripts from an early version
of NCSA httpd (pre-1.0, I believe). I think NCSA were at least talking
about dropping it themselves for 1.5...

rst