Project

General

Profile

Actions

Bug #21216

closed

All rudder commands using the API don't detect the port of the webapp when we configure a virtualhost with a different port

Added by Nicolas CHARLES over 2 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
N/A
Category:
Server components
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Medium
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No

Description

If the webapp/API listen on another port (because of ease of distinction of target for virtualhost) then the commands won't work, as they'll probably talk to 443
Detection of port is made with

get_https_port() {
  # get port from configuration
  PORT=$(agent_conf https_port)
  # if not trust the server on this
  if [ "${PORT}" = "" ] && [ -f "${RUDDER_JSON}" ]; then
    PORT=$(rudder_json_value 'HTTPS_POLICY_DISTRIBUTION_PORT')
  fi
  # else default to 443
  if [ "${PORT}" != "" ]; then
    PORT=":${PORT}" 
  fi
  echo "${PORT}" 
}

which is for the policy distribution, and not the webapp

There is nowhere yet where to store this value, so we'll probably need a new config parameter


Related issues 1 (0 open1 closed)

Related to Scale-out relay - Bug #22290: Script node to relay don't detect webapp port when we configure a virtualhost with a different portReleasedAlexis MoussetActions
Actions

Also available in: Atom PDF