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

Update OkHTTP to allow to use HTTP/2 #244

Open
BenDevelopment opened this issue Apr 6, 2017 · 6 comments
Open

Update OkHTTP to allow to use HTTP/2 #244

BenDevelopment opened this issue Apr 6, 2017 · 6 comments

Comments

@BenDevelopment
Copy link

I suggest to update the OkHTTP package to make it works with http/2.
It can fix REFUSED_STREAM errors on https request.
Someone can do this?

@Cheesebaron
Copy link
Contributor

If you look at this repo it is pretty much dead. I think there are some forks updating OkHTTP.

@paulcbetts could we maybe give someone willing to bring ModernHttpClient up to snuff access to the repo or something like that?
I know there is Xamarin's HttpClient handler for Android that does pretty much what you do here. But only on Android 5.x and up.

@BenDevelopment
Copy link
Author

BenDevelopment commented Apr 6, 2017

@Cheesebaron can you give me some details about Xamarin's HttpClient handler for https?
Edit: I think your are talking about that: https://developer.xamarin.com/guides/android/application_fundamentals/http-stack/

@nicolasesprit
Copy link

And for the PRO version (paid) subscribers too. Many thanks !

@Cheesebaron
Copy link
Contributor

@nicolasesprit with the pro version you pay for:

The only feature difference between ModernHttpClient and ModernHttpClient Pro is the ability to use untrusted SSL/TLS certificates - there is no performance or other internal differences between the two versions

You pay for untrusted SSL/TLS, not for stability or anything else regarding this library. It still fulfils that. You could also just have paid, nothing at all and used a lets encrypt cert or similar.

@nicolasesprit
Copy link

Of course

@justintoth
Copy link

We just moved our Mobile API from a windows server 2012 instance to a 2016 instance, which supports HTTP/2. Immediately the connectivity in our Xamarin iOS and Android apps stopped working, which leverage ModernHttpClient. Is the recommended approach to now switch over to AndroidClientHandler?

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