Skip to content

Why could not SSL connection be established? #1779

Answered by raman-m
harshwd asked this question in Q&A
Discussion options

You must be logged in to vote

System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)

It seems you tried to connect to Azure container which had specific version of HTTP.
Based on your route and log record (see above), I would say that you tried to connect from Ocelot app using HTTP1 version protocol, but possibly your Azure container had another version of HTTP aka HTTP/2+.
To provide correct setting of HTTP version protocol, you need to use DownstreamHttpVersion property of the route.

And, you need more tests...

  1. Try to fallback your https scheme to http and check the behavior of the route.
  2. If http scheme works perfectly, then you …

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by raman-m
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
question Initially seen a question could become a new feature or bug or closed ;) Websockets Ocelot feature: Websockets
2 participants
Converted from issue

This discussion was converted from issue #1625 on November 06, 2023 08:11.