* Geoffrey Young <[EMAIL PROTECTED]> wrote:
> we have the following entries in CHANGES under 2.1-dev:
>
> *) Drop the ErrorHeader directive which turned out to be a misnomer.
> Instead there's a new optional flag for the Header directive
> ('always'), which keeps the former ErrorHeader functionality.
> [Andr� Malo]
>
> *) mod_headers: Allow 'echo' also for ErrorHeaders. [Andr� Malo]
>
> *) Bring ErrorHeader concept forward from 1.3, so that response
> header fields can be set for return even on errors or external
> redirects. [Ken Coar]
>
> ErrorHeader appears to have been removed from the 2.0 branch as of 2.0.51.
>
> I guess it depends on how you view CHANGES, but from my pov I would expect
> it to just list tangible changes from, say, 2.0.53 to 2.2. since
> ErrorHeader won't exist in 2.0.53 (or whatever the most recent release ends
> up being) and won't exist in 2.2 maybe removing these from CHANGES
> altogether is warranted?
In this case, I think, no. It's clearly stated in 2.0, that's a backport from
the development branch (since it were different changes to the code base).
In most cases it *was* removed from 2.1 change log.
nd
--
Winnetous Erbe: <http://pub.perlig.de/books.html#apache2>
