Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added custom headers support for WebSocket connection (502) #554

Merged
merged 1 commit into from
Jun 18, 2018

Conversation

vit21ik
Copy link
Contributor

@vit21ik vit21ik commented Jun 8, 2018

Signed-off-by: Vitalii Vlasiuk vvlasuk@gmail.com

#502

Minor fix that allow use custom headers in request using WebSockets :

Added new parameter "customHeaders" to MqttConnectOptions
Pass this param to WebSocketHandshake
Added new custom headers to handshake request

Please make sure that the following boxes are checked before submitting your Pull Request, thank you!

  • [*] This change is against the develop branch, not master.
  • [*] You have signed the Eclipse ECA
  • [*] All of your commits have been signed-off with the correct email address (The same one that you used to sign the CLA) Hint: use the -s argument when committing.
  • [*] If This PR fixes an issue, that you reference the issue below. OR if this is a new issue that you are fixing straight away that you add some Description about the bug and how this will fix it.
  • If this is new functionality, You have added the appropriate Unit tests.

Signed-off-by: Vitalii <vitalii.vlasiuk@temy.co>
@jpwsutton jpwsutton merged commit d669d22 into eclipse:develop Jun 18, 2018
@jpwsutton
Copy link
Member

Thanks for this @vit21ik! I've merged that in and updated it to work with the Network Module Service enhancement in PR #440

@@ -39,6 +39,7 @@
private String uri;
private String host;
private int port;
private Properties customWebSocketHeaders;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And why is it a Properties field now, instead of a Map? Properties is deprecated and the reading/writing abilities of Properties are not used in this case? Can I issue a PR to change this to Map please?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Properties is used for sslClientProps.
Sure, Map is better.
New pull request - #555

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants