Bug 805364 - Trailing slash causes csprocessor.cfg / .ini server urls to not match
Summary: Trailing slash causes csprocessor.cfg / .ini server urls to not match
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CSProcessor
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Lee Newson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-21 02:49 UTC by Joshua Wulf
Modified: 2014-10-19 23:00 UTC (History)
2 users (show)

Fixed In Version: 0.22.4
Clone Of:
Environment:
Last Closed: 2013-06-07 01:29:26 UTC
Embargoed:


Attachments (Terms of Use)

Description Joshua Wulf 2012-03-21 02:49:24 UTC
If you put a trailing slash on a server url in the csprocessor.ini file, and the server url does not have a trailing slash in the .cfg file, they won't match.

Obviously they are not the same string, but putting either url into a browser would get a similar result:

https://skynet.usersys.redhat.com:8443/TopicIndex/
https://skynet.usersys.redhat.com:8443/TopicIndex

both take you to the same place in a browser. So that user expectation can carry over into the configuration.

Maybe remove any trailing slash when matching urls?

Comment 1 Lee Newson 2012-03-24 03:55:30 UTC
Fixed in 0.22.4

Cause:
The Java URL.equals() function doesn't return that those two URL's are equal. (There is a reason but not worth mentioning)

Consequence:
The client would return an error message that the csprocessor.cfg couldn't be matched to a server configuration.

Fix:
Run all the URL's from the Command Line, csprocessor.cfg and csprocessor.ini through a validation function to add the trailing slashes and make sure that the protocal is set.

Comment 2 Lee Newson 2013-06-07 01:29:26 UTC
Closing and setting as current release as no QA was performed by the original reporter. If there is still an issue with this bug still than please re-open it.


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