thank you everyone. Changes made and they work.
Point taken about being invalid for 15 years. I inherited an old
application/setup.
Again, thank you all.
From: Frank Gingras
Sent: Monday, July 1, 2024 3:03 PM
To: users@httpd.apache.org
Subject: [External] :
On Mon, Jul 1, 2024 at 2:53 PM Eric Covener wrote:
> On Mon, Jul 1, 2024 at 2:51 PM Matthew Goebel
> wrote:
> >
> > Going from 2.4.59 to 2.5.60 I had to make the following change in my
> httpd.conf file.
> >
> > AddType application/x-httpd-php .php
> >
> > to
> >
> > AddHandler
On Mon, Jul 1, 2024 at 2:51 PM Matthew Goebel wrote:
>
> Going from 2.4.59 to 2.5.60 I had to make the following change in my
> httpd.conf file.
>
> AddType application/x-httpd-php .php
>
> to
>
> AddHandler application/x-httpd-php .php
Thanks Matthew, this makes perfect sense. I will add this
On Mon, Jul 1, 2024 at 2:45 PM Jack Swan wrote:
>
> Have an existing application and Apache installation (have been using Apache
> for years).
>
> Upgraded Apache from 2.4.59 to 2.4.60 today and the browser prompts to save
> the index.php file instead of
> serving/processing it when just
Going from 2.4.59 to 2.5.60 I had to make the following change in my
httpd.conf file.
AddType application/x-httpd-php .php
to
AddHandler application/x-httpd-php .php
Thanks,
Matt
On Mon, Jul 1, 2024 at 2:45 PM Jack Swan
wrote:
> Have an existing application and Apache installation (have
Have an existing application and Apache installation (have been using Apache
for years).
Upgraded Apache from 2.4.59 to 2.4.60 today and the browser prompts to save the
index.php file instead of
serving/processing it when just entering https:// as the URL. This
had been working fine for years
