[TINKERPOP-2488] Using ws:// when Neptune requires wss:// doesn't throw exception

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Cannot Reproduce
• Affects Version/s: 3.4.8
• Component/s: javascript
• Assignee: Unassigned
• Reporter: Mark Richman
• Created: 08/Dec/20 14:41
• Updated: 05/Mar/21 20:57
• Resolved: 05/Mar/21 20:57

Description

When using the JavaScript driver, attempting to connect to Neptune via ws:// when Neptune requires wss:// does not throw an exception. The process simply exits silently.

#!/usr/bin/env node

import pkg from 'gremlin';
const { structure, process, driver } = pkg;
const Graph = structure.Graph;
const __ = process.statics;
const { t, order, cardinality, column, scope, pop, operator, P, traversal } = process;
const hostname = 'neptunecluster.cluster-xxxxxxxxx.us-east-1.neptune.amazonaws.com'
const port = 8182
const wspath = `ws://${hostname}:${port}/gremlin`; // doesn't throw exception if wss:// is required
const DriverRemoteConnection = driver.DriverRemoteConnection;
const connection = new DriverRemoteConnection(wspath, {});
const g = traversal().withRemote(connection);

const result = await g.V().hasLabel("person").toList()
console.log(result)

 
Note: using Node.js as a shell script like this requires "type": "module" in package.json