BoazDr commented on issue #5103: URL: https://github.com/apache/apisix/issues/5103#issuecomment-925768300
> You could give some replication steps and points of blocking, such as adding a route and setting an SSL certificate, sending a request that hits the route, but doesn't hit it. Something like this would allow us to reproduce the problem. First of all, thank you for the fast and informative replies, much appreciated. I can't realy reproduce it because it is a sensitive project at work, but I will try explaining it in high level it might help: We have a web written in javascript, which inside connects through websocket to a remote recognition engine. I changed the websocket connection url in the JS code to point to APISIX host and from there it should redirect to the actual websocket. While doing it with normal websockets (ws://) everything works fine, but when trying to change the url to secured websockets I'm getting '400 Bad Request'. The changes I've done are: changed the port to 443 in upstream host, scheme to https without tcp, created new SSL with certificate and key of the linux engine machine. But still getting the same error everythime - the websocket connection cant be established. Can't figure out what am I doing wrong, downloaded WireShark and TShark for network observation and tried comparing both networks transactions while on ws and wss, no real value yet. The thing I realy need is a good and working example of simple cmd commands to run some secured ws, all the docs are not that informative imo. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
