Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When using the Thin + Apache setup, URLs arrive at Rails with an extra forward slash just after the prefix.  This is known to break the retrievable of search history for the fancy queries drop-down on pages with tupane search.  (e.g.  GET "/katello//organizations/auto_complete_search?search=organ" )

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


How reproducible:
Always

Steps to Reproduce:
1. Start up Katello via Apache+Thin: 
RAILS_RELATIVE_URL_ROOT=/katello ./script/thin  start --config /etc/katello/thin.yml   --rackup config.ru

2. Navigate to Systems page
3. Check Rails logs to see details of request
  
Actual results:
Requests have an extra forward slash after the prefix in them: "/katello//organizations/auto_complete_search?search=organ"

Expected results:
No extra slash:
"/katello/organizations/auto_complete_search?search=organ"

Additional info:

git commit - 4f258b9118b9a360dfc3c09283bb6e95fa0ea609

Resolved the issue of the unnecessary / in the resources; however, recent changes to move search to elasticsearch has caused search history to not work properly.  That issue is documented in bug 782518.

Test notes:

<bbuckingham> what you can do, is to monitor the production.log and see that requests from the browser to not have the extra /

Verified.

getting rid of 6.0.0 version since that doesn't exist