[KNOX-1996] For websocket connections, backend url generated is incorrect - has an extra '/' in path

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0, 1.1.0, 1.2.0, 1.3.0
• Fix Version/s: 1.4.0
• Component/s: Server
• Environment: HDP 3.1.0
• Assignee: Rajat Goel
• Reporter: Rajat Goel
• Created: 27/Aug/19 11:53
• Updated: 01/Oct/19 19:15
• Resolved: 01/Oct/19 19:15

Description

For websocket connections, while generating backend url in org.apache.knox.gateway.websockets.GatewayWebsocketHandler (getMatchedBackendURL() API), Knox appends 'pathservice[1]' to 'backend' StringBuffer if Service url doesn't end with '/ws'. As a result, URI generated had an extra '/' eg: ws://rafd001-mst-01.cloud.in.guavus.com:11011//_sock/411/anq2kfzp/websocket and my UI backend which uses SockJS lib was not responding for 2 minutes and eventually closing connection.

Correct Url which should have been generated is: ws://rafd001-mst-01.cloud.in.guavus.com:11011/_sock/411/anq2kfzp/websocket

Issue Links

• links to: GitHub Pull Request #142