Bug 888128 - Unable to match Server configurations when missing slashes
Summary: Unable to match Server configurations when missing slashes
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: pressgang-ccms-dev
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-18 03:34 UTC by Lee Newson
Modified: 2013-06-07 01:29 UTC (History)
1 user (show)

Fixed In Version: 0.28.5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-07 01:29:48 UTC


Attachments (Terms of Use)

Description Lee Newson 2012-12-18 03:34:25 UTC
Given the following settings:

csprocessor.ini

    # Production Server settings
    production.url=http://localhost:8080/TopicIndex
    production.username=jwulf

csprocessor.cfg

    SPEC_ID=12807
    SERVER_URL=http://localhost:8080/TopicIndex

The following error occurs:

ERROR: No credentials are setup for the "http://localhost:8080/TopicIndex" server specified in the csprocessor.cfg file. Please setup the server in your csprocessor.ini configuration file.


Workaround:

You can work around this error by adding the trailing slash in the csprocessor.cfg file. eg:

csprocessor.cfg

    SPEC_ID=12807
    SERVER_URL=http://localhost:8080/TopicIndex/

Comment 1 Lee Newson 2012-12-18 23:32:17 UTC
Fixed in version 0.28.5.

Cause:

The java URI equals method assumes that the above two mentioned URL's are different. The csprocessor.ini is run through a method to clean it and make sure it is standard, however the csprocessor.cfg did not.

Consequence:

You'd get the error above.

Fix:

Run the csprocessor.cfg url's through the same cleaning and validation method.

Comment 2 Lee Newson 2013-06-07 01:29:48 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.