-
Notifications
You must be signed in to change notification settings - Fork 126
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
Pusher not properly setting headers on HTTP requests #687
Comments
Ok my college just came up with an ugly solution involving reflection.
This works, but is far from ideal. Maybe there's a hidden bug somewhere, since there actually is a property |
Of course stuff using reflection will work but that means you are depending on implementation details. We don't offer a way to make authenticators like this, but the way you are doing it is exactly the same as our new I have made a sample for this on a branch, and you can see the flow starting here. |
That being said, I just ran the unit test that tests the Headers property and it passed. EDIT Ok that test only tests the puller. And you are using a pusher. I see the problem now. It's a very small fix, and you are lucky you reported today because code freeze is just in a couple of hours ;). |
Things should be fixed now, let me know in a day or two, or I'll be closing this ticket. |
Thanks a lot for your fast response and action, this looks like it would resolve our issue. Is there an easy way for us to test this, like a private NuGet feed? Otherwise I'll just build and reference locally. |
Get a build from our nightly build server |
Perfect! Just tested, the headers which we set via |
Estimated by the end of this month |
Hi,
we're currently looking into implementing a custom authorization scheme.
Basically, all we'd need to do is to send an Authorization Header with each request, however we're struggling in achieving this simple thing. Looking into the code it seems like
ICustomHeadersAuthorizer
should be the way to go, however all the interfaces inCouchbase.Lite.Auth
seem to be internal.I'm currently looking into re-packaging a custom version of Couchbase.Lite, however that's something I'd really like to avoid. So before getting my hands dirty I was wondering about two things:
I'd be more than happy in providing a helping hand and pull requests if necessary.
Thanks a lot in advance,
Daniel
The text was updated successfully, but these errors were encountered: