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

JetFire does not provide a mechanism for using client side certificates #65

Open
nathanday opened this issue May 24, 2017 · 3 comments
Open

Comments

@nathanday
Copy link

More of a suggestion than a issue, I needed to use client side certificates, the way I got around this was to create a dictionary property on JFRWebSocket called additionalOutputStreamProperties which is then enumerated over applying the setProperty:forKey: for each entry to the output stream, adding something like this to JetFire would make it easy to handle any niche use case.

@acmacalister
Copy link
Owner

Agreed this is the feature request. I believe this is related to the same request we got on daltoniam/Starscream#271

@vkolosovsky
Copy link

vkolosovsky commented Nov 17, 2017

Is there any progress on this?

@jarrillaga
Copy link

@nathanday Did you achieve to use Client side certificates ? Can you share you code of WebSocket.swift ?

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

No branches or pull requests

4 participants