update to apache2_2.4.52-1ubuntu4.9_amd64 causes website to respond with 301 redirect to itself

Bug #2061740 reported by Blair
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)

Bug Description

Hi, I have a wordlpress site running on Ubuntu 22.04.3 LTS (GNU/Linux 6.2.0-1017-aws x86_64).

After updating apache2 the site returns a 301 redirect to itself. No other configuration was changed.

~$ apache2 -v
Server version: Apache/2.4.52 (Ubuntu)
Server built: 2023-10-26T13:44:44

** site is working

Now we update apache2
~$ sudo apt update

~$ sudo apt-get install --only-upgrade apache2
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  apache2-bin apache2-data apache2-utils
Suggested packages:
  apache2-doc apache2-suexec-pristine | apache2-suexec-custom www-browser
The following packages will be upgraded:
  apache2 apache2-bin apache2-data apache2-utils
4 upgraded, 0 newly installed, 0 to remove and 120 not upgraded.
Need to get 1698 kB of archives.
After this operation, 3072 B of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 apache2 amd64 2.4.52-1ubuntu4.9 [97.9 kB]
Get:2 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 apache2-bin amd64 2.4.52-1ubuntu4.9 [1347 kB]
Get:3 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 apache2-data all 2.4.52-1ubuntu4.9 [165 kB]
Get:4 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 apache2-utils amd64 2.4.52-1ubuntu4.9 [88.7 kB]
Fetched 1698 kB in 0s (31.4 MB/s)
(Reading database ... 78982 files and directories currently installed.)
Preparing to unpack .../apache2_2.4.52-1ubuntu4.9_amd64.deb ...
Unpacking apache2 (2.4.52-1ubuntu4.9) over (2.4.52-1ubuntu4.7) ...
Preparing to unpack .../apache2-bin_2.4.52-1ubuntu4.9_amd64.deb ...
Unpacking apache2-bin (2.4.52-1ubuntu4.9) over (2.4.52-1ubuntu4.7) ...
Preparing to unpack .../apache2-data_2.4.52-1ubuntu4.9_all.deb ...
Unpacking apache2-data (2.4.52-1ubuntu4.9) over (2.4.52-1ubuntu4.7) ...
Preparing to unpack .../apache2-utils_2.4.52-1ubuntu4.9_amd64.deb ...
Unpacking apache2-utils (2.4.52-1ubuntu4.9) over (2.4.52-1ubuntu4.7) ...
Setting up apache2-bin (2.4.52-1ubuntu4.9) ...
Setting up apache2-data (2.4.52-1ubuntu4.9) ...
Setting up apache2-utils (2.4.52-1ubuntu4.9) ...
Setting up apache2 (2.4.52-1ubuntu4.9) ...
Installing new version of config file /etc/apache2/mods-available/setenvif.conf ...
apache-htcacheclean.service is a disabled or a static unit not running, not starting it.
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for ufw (0.36.1-4ubuntu0.1) ...
Scanning processes...
Scanning linux images...

Running kernel seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.

~$ apache2 -v
Server version: Apache/2.4.52 (Ubuntu)
Server built: 2024-04-10T17:45:18

** after the update the site has the 301 issue

Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

Thank you for taking the time to file a bug report.

I installed the latest version of apache2 (Jammy) here and could not reproduce the issue. Could you please provide a minimal reproducer so that we can determine if this is indeed a problem with the package? If you could, please provide the configuration files for apache2 that you are using (make sure to remove any confidential/personal information from them).

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".

For local configuration issues, you can find assistance here:

Changed in apache2 (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for apache2 (Ubuntu) because there has been no activity for 60 days.]

Changed in apache2 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.