You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this is a bug or intended behavior in istio.
For example, with a total of 2 workloads set up as shown below, a curl request to a.example.com results in the error "error:0A00010B:SSL routines::wrong version number".
My prediction is that based on the host header of "init.example.com / a.example.com", init.example.com should output an error and a.example.com should output the normal value. Or at least output the error when trying to register the second gateway server.
However, if I request any host and the port is 443, I get the same error.
I realize this is my mistake. It was a typo.
However, I don't see any logs of this issue.
I was wondering if this is the intended behavior, or if istio doesn't leave any logs.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I don't know if this is a bug or intended behavior in istio.
For example, with a total of 2 workloads set up as shown below, a curl request to a.example.com results in the error "error:0A00010B:SSL routines::wrong version number".
My prediction is that based on the host header of "init.example.com / a.example.com", init.example.com should output an error and a.example.com should output the normal value. Or at least output the error when trying to register the second gateway server.
However, if I request any host and the port is 443, I get the same error.
I realize this is my mistake. It was a typo.
However, I don't see any logs of this issue.
I was wondering if this is the intended behavior, or if istio doesn't leave any logs.
Beta Was this translation helpful? Give feedback.
All reactions