Bug 749805 - Extra forward slash in URL with Thin
Summary: Extra forward slash in URL with Thin
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: katello-blockers
TreeView+ depends on / blocked
 
Reported: 2011-10-28 13:52 UTC by Eric Helms
Modified: 2019-09-26 13:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 18:03:25 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Eric Helms 2011-10-28 13:52:27 UTC 
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:
Comment 1 Brad Buckingham 2012-01-17 19:02:25 UTC 
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.
Comment 2 Corey Welton 2012-01-19 15:43:36 UTC 
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 /
Comment 3 Corey Welton 2012-01-19 22:01:58 UTC 
Verified.
Comment 6 Mike McCune 2013-08-16 18:08:26 UTC 
getting rid of 6.0.0 version since that doesn't exist
Note You need to log in before you can comment on or make changes to this bug.