Bug 433098 - URL rewrite problem on satellite 5 on directory URL's without ending slash
URL rewrite problem on satellite 5 on directory URL's without ending slash
Product: Red Hat Satellite 5
Classification: Red Hat
Component: WebUI (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Shannon Hughes
Brandon Perkins
Depends On:
  Show dependency treegraph
Reported: 2008-02-16 04:35 EST by Kurt Keller
Modified: 2009-02-10 13:49 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-02-10 13:49:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kurt Keller 2008-02-16 04:35:55 EST
Description of problem:

When accessing a couple of URL's without slash at the end cause the
server part of the URL to be rewritten.
For example: 

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
1. setup a satellite server, using your.satellite as hostname
2. change the hostname of the machine to your.machine and restart
3. access the satellite with https://your.satellite/....
Actual results:

The mentioned links (and possibly others) do a URL rewrite from
https://your.satellite/... (the 'service' name of the satellite) to
https://your.machine/... (the 'machine' name of the satellite)

When the mentioned URL's are written with a slash at the end, then the
rewrite does not happen and all is fine.

Expected results:

No change in the server name part of the URL

Additional info:

Actually the bug does not bother me in my own environment, as I do have an
apache rewrite config installed anyway, so we can access the satellite also
by short name, rather than FQDN and still have authentication cookies etc.
working just fine. The piece of config causes apache to rewrite any requests
coming in and not being in the satellite's FQDN service name format to be
rewritten and the browser referred to the correct URL. Maybe you want to
include this small piece of config in a future satellite update:

cat /etc/httpd/conf/rhn/rhn/rewrite.conf

# ------------------------------------------------------------------------------
# ------------------------------------------------------------------------------

# uri rewriting
RewriteEngine           On
RewriteLog              "logs/rewrite_log"
RewriteLogLevel         0

# change the host to a fully qualified service name which is
# what everybody should connect to; this is required because
# cookies may be set which are associated with the hostname
RewriteCond     %{HTTP_HOST}    !^your\.sytellite [NC]
RewriteRule     ^/(.*)$         https://your.satellite/$1   [NC,R=301,L]

# ------------------------------------------------------------------------------
Comment 1 Clifford Perry 2009-02-10 13:49:12 EST
Hi there, 
I am going to close this out as WONTFIX, due to the fact that this proposed change is in conflict with the statement within our documentation that Satellite is installed on a server with FQDN (satellite.example.com) vs using just satellite. 

I do think though that your feedback may be of interest to the Spacewalk community where Spacewalk instances are not always created for production environments. 


Note You need to log in before you can comment on or make changes to this bug.