Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Support Questions

Find answers, ask questions, and share your expertise
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

NiFi websocket subprotocols support

avatar
Reader

 

Hello,

For a project, I need to configure a WebSocket connection using NiFi. I also need to define a custom sub-protocol in the “Sec-WebSocket-Protocol” header.

I have seen that some custom headers can be defined in the parent FF with the “header.Something” attribute. In fact, all headers are defined except for the sub-protocol. How can I achieve this without having to develop my own processor?

My GenerateFlowFile has the following attributes: `header.Sec-WebSocket-Protocol = Test` and another `header.Test = Test2`.

The request retrieved by Wireshark only uses header.Test. Is it normal ?
Thanks.

(related to https://community.cloudera.com/t5/Support-Questions/Nifi-websocket-subprotocols/m-p/311764#M224816 and https://community.cloudera.com/t5/Support-Questions/NiFi-WebSocket-Headers/m-p/361488)

1 REPLY 1

avatar
Community Manager

@Tituya Welcome to the Cloudera Community!

To help you get the best possible solution, I have tagged our NiFi experts @MattWho @mburgess  who may be able to assist you further.

Please keep us updated on your post, and we hope you find a satisfactory solution to your query.


Regards,

Diana Torres,
Senior Community Moderator


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Learn more about the Cloudera Community: