Project

General

Profile

Actions

Bug #3569

closed

Port in use by the browser is used in rendering the templates

Added by Greg Sutcliffe about 11 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Unattended installations
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

We fixed the hostname version of this issue a while back, but the port got missed. If you use a non-standard port to access foreman, it'll be written into your templates, which makes tunnelling in from home a real pain.

We should update :foreman_url to be a real url and then parse it for the host and port


Related issues 5 (0 open5 closed)

Related to Foreman - Bug #3210: We set foreman_url to foreman.domain by defaultClosedGreg Sutcliffe10/08/2013Actions
Related to Foreman - Feature #717: Add an option to overwrite foreman_url value for reverse proxy useResolved03/08/2011Actions
Has duplicate Foreman - Bug #2559: in foreman_url() Port is still copied from users browserClosedGreg Sutcliffe05/24/2013Actions
Has duplicate Foreman - Bug #1461: preseed URL hardcoded to http (patch)Resolved01/20/2012Actions
Precedes Foreman - Bug #3659: "no implicit conversion of URI::HTTP into String" running rake reports:summarizeClosedDominic Cleal11/05/201311/05/2013Actions
Actions

Also available in: Atom PDF