-
Notifications
You must be signed in to change notification settings - Fork 537
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
Update Headers on Reconnect #282
Comments
any interest in this? |
Sorry for not replying earlier (somehow missed this one; there have been significant changes since it was raised!). |
I was just looking through my code and realized I had a comment about this issue, so I decided to look into it again. Didn't realize that 1.3+ has been released. I was looking at the changes and noticed this PR which is basically what I am looking for I think? I would have to test it. Do you think that would work? or should we update the For my use case I get my auth first then create the connection by setting headers. I was never able to use auto reconnect because It would try to reconnect with a bad auth token. With the |
I think |
Sorry - just noticed that you were talking about |
Yes, i forgot to post the link to #283 |
#283 fixes the issues of reconnection headers by adding the headers on reconnection attempt. Will re-open if it does not work for my use case. Thanks. |
I am connecting to aws IoT using a custom authorizer. To do this i am using the
SetHTTPHeaders
to add additional headers during connection. It would be nice if we could also do this on reconnect. There is a way to provide credentials on reconnect but that doesn't work for me, need to add additional headers.The text was updated successfully, but these errors were encountered: