Project

General

Profile

Actions

Feature #717

closed

Add an option to overwrite foreman_url value for reverse proxy use

Added by Jeff Weiss over 13 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Unattended installations
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Old title : Foreman UI passes wrong urls to backend config files

I have foreman running on a private subnet. I forward a port from hostbox to foreman-box so that I can access the foreman UI from a browser. While I access foreman at http://hostbox:5000/, it's actually running on http://foreman-box:3000/.

The problem shows up when I do "Build PXE Default".

[root@jweiss-foreman-1 tftpboot]# more pxelinux.cfg/default
DEFAULT menu
PROMPT 0
MENU TITLE PXE Menu
TIMEOUT 200
TOTALTIMEOUT 6000
ONTIMEOUT local

LABEL local
MENU LABEL (local)
MENU DEFAULT
LOCALBOOT 0

LABEL Kickstart Default - hg1
kernel boot/JeffLinux-1.0-x86_64-vmlinuz
append initrd=boot/JeffLinux-1.0-x86_64-initrd.img ks=http://hostbox:5000/unattended/template/Kickstart%20Default/hg1 ksdevice=bootif network kssendmac

-----------
notice the use of "hostbox" in the ks attribute. Hosts on the private subnet should not be connecting to foreman that way. Foreman not be taking the HTTP headers from one user's browser session and using that as foreman's official address in PXE configs.

This is foreman-0.1.7-rc5.1.noarch rpm


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #3569: Port in use by the browser is used in rendering the templatesClosedGreg Sutcliffe11/04/2013Actions
Actions

Also available in: Atom PDF