> Then how do you propose those using it, as lets say in my example, set the
> cgi directory for that vhost?
They can keep using it, get the equivalent function from a default
configuration and never be the wiser, or use/change to Alias + an
explicit SetHandler and Options.
Most default configu
On 10/10/2021 11:07, Eric Covener wrote:
I'm talking about removing it from the default configuration file and
marking it as deprecated.
I don't see a negative impact to users with their own configuration
(not changed) or users
with our default configuration (since the alternative does the same
On Sat, Oct 9, 2021 at 8:30 PM Noel Butler wrote:
> On 10/10/2021 03:39, Eric Covener wrote:
>
> Relative to the recent CVEs, should we replace ScriptAlias in the
> default conf with Alias + SetHandler cgi-script in the corresponding
> Directory section?
>
> And .. should ScriptAlias be deprecate
… both +1 and -1.
A change in version number or major version can imply significant changes in
the base configuration, and I see this suggestion as a fit for a httpd-2.5,
-3.0 or the likes. Hence, +1.
However changing such widely used setting on the existing 10 year old 2.4 tree
will cause ope
On 10/10/2021 03:39, Eric Covener wrote:
Relative to the recent CVEs, should we replace ScriptAlias in the
default conf with Alias + SetHandler cgi-script in the corresponding
Directory section?
And .. should ScriptAlias be deprecated/discouraged in some way if the
expanded version is safer by
Relative to the recent CVEs, should we replace ScriptAlias in the
default conf with Alias + SetHandler cgi-script in the corresponding
Directory section?
And .. should ScriptAlias be deprecated/discouraged in some way if the
expanded version is safer by avoiding the equivalent of setting the
handl