Project

General

Profile

Actions

Bug #25675

closed

Add 127.0.0.1 as ServerAlias for multi-vhost server configuration

Added by Michel BOUISSOU about 2 months ago. Updated about 1 month ago.

Status:
Released
Priority:
N/A
Category:
Relay server or API
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Very Small
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No

Description

When the 2 rudder vhosts run on the same IP address and port, only the ServerName and ServerAlias can differenciante between them, and wildcard use on the VirtualHost entry may be unreliable.

As the default configuration of the Rudder agent that runs ont the Rudder server itself specifies “127.0.0.1” as policy server, we want to make sure that a call to 127.0.0.1 is routed to the correct vhost.

So we need to add a “ServerAlias 127.0.0.1” entry to the proposed multi-vhost server configuration.

Actions #1

Updated by Michel BOUISSOU about 2 months ago

  • Status changed from New to In progress
Actions #2

Updated by Michel BOUISSOU about 2 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Michel BOUISSOU to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/5945
Actions #3

Updated by Michel BOUISSOU about 2 months ago

  • Status changed from Pending technical review to Pending release
Actions #4

Updated by Alexis Mousset about 1 month ago

  • Fix check changed from To do to Checked
Actions #5

Updated by Vincent MEMBRÉ about 1 month ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 8.1.8 and 8.2.1 which were released today.

Actions

Also available in: Atom PDF