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.
Category:
Unattended installations
|
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
- Status changed from Assigned to Ready For Testing
- Assignee set to Greg Sutcliffe
- Has duplicate Bug #2559: in foreman_url() Port is still copied from users browser added
- Related to Bug #3210: We set foreman_url to foreman.domain by default added
- Translation missing: en.field_release set to 2
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Has duplicate Bug #1461: preseed URL hardcoded to http (patch) added
- Related to Feature #717: Add an option to overwrite foreman_url value for reverse proxy use added
- Precedes Bug #3659: "no implicit conversion of URI::HTTP into String" running rake reports:summarize added
Also available in: Atom
PDF