Fyodor_A's avatar
Fyodor_A
SmartBear Alumni (Retired)
6 years ago
Status:
New Idea

Make Collaborator client support context path.

Submitting on behalf of Clue Technologies SL:

We have configured the Collaborator instance to use a non-root context path, so we can route the connections under our own subdomain. The steps we followed are detailed below:
- The file <Collaborator Installation dir>/tomcat/conf/Catalina/localhost/ROOT.xml has been renamed to context.xml.default
- The webapp directory <Collaborator Installation dir>/tomcat/webapps/ROOT has been renamed to our context path name (in our case "reviews")

 

As a result, the WebUI is accessible at the.server.net/reviews

 

Currently, the Collaborator client doesn't support the context path. It ignores everything you type after "subdomain.example.com/" and tries to find the API at 'subdomain.example.com/services/json/v1' instead of 'subdomain.example.com/reviews/services/json/v1'

 

The request is to make the Collaborator client support connecting to a non-root context path

No CommentsBe the first to comment