Bug 749805

Summary:	Extra forward slash in URL with Thin
Product:	Red Hat Satellite	Reporter:	Eric Helms <ehelms>
Component:	WebUI	Assignee:	Brad Buckingham <bbuckingham>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.1	CC:	cwelton, mmccune
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-22 18:03:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	747354

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