Member since
01-08-2018
4
Posts
0
Kudos Received
0
Solutions
02-12-2018
06:49 PM
Anyone out there have any hints or tips on this?
... View more
01-08-2018
11:34 AM
okay, so you decided not to use Nifi for you websocket client?
... View more
01-08-2018
09:49 AM
Hi @Balakrishna Dhanekula Were you able to find a solution to this issue yet? I'm also trying to use the ConnectWebSocket processor with a basic header, but I'm having the same problem as you. I asked a question in the forum before seeing yours ( https://community.hortonworks.com/questions/157914/nifi-connectwebsocket-processor-failing-how-to-add.html)
... View more
01-08-2018
09:44 AM
Hello,
I'm trying to use Nifi to connect to a secure WebSocket (wss:// .... ). I'm having trouble connecting to the stream because of a very basic authentication issue.
I've used wscat (npm) and a Java client to successfully connect in the past. All that was needed is an Http Header.
The wscat implementation would only require the following option: .option('-H, --header <header:value>', 'Set an HTTP header. Repeat to set multiple. (--connect only)', appender(), []) But, when I add the header as a property to the ConnectWebSocket processor and/or the JettyWebSocketClient, Nifi complains that it is not a supported property. Since SSL context services are not required to connect to this particular stream, is there a way that I can still connect just using a custom header?
... View more
Labels:
- Labels:
-
Apache NiFi