Apache traffic server on forward mode does not pass websocket
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Apache traffic server on forward mode does not pass websocket
Hi, I configure my traffic server with its website guideline (only remove x-forward and via header). But I have a problem with wss requests. On network panel of firefox developer tools, there is no response, it shows error:
The connection to fetch this resource was not secure
Hi, I configure my traffic server with its website guideline (only remove x-forward and via header). But I have a problem with wss requests. On network panel of firefox developer tools, there is no response, it shows error:
The connection to fetch this resource was not secure
How can I fix it?
That message simply means you've asked for a secure connection and the server is not capable of providing it -- either because it does not have a certificate or it's not configured correctly to use a certificate.
The main connection is based on https, and the certificate is ok, but for any websocket request, its gave a certificate error. Its not just for an website, apache traffic server gave the error for all domain. And yes, this is my server, I have full access on it.
The main connection is based on https, and the certificate is ok, but for any websocket request, its gave a certificate error. Its not just for an website, apache traffic server gave the error for all domain. And yes, this is my server, I have full access on it.
I'd not heard of websockets prior to this, so can only speculate: Perhaps the certificate doesn't cover the URI that the websocket is using? I know the certs I use only cover domain.com and www.domain.com -- other URLs or sub-domains are not included. Again, I'm just guessing. Mayhaps someone else will chime in.
I use apache traffic server as forward proxy, not as reverse proxy, so the certificate(s) is not mine. While I request any website, that contain ws (websocket) request, the whole site will be loaded except websocket part!
Apache traffic server on forward mode does not pass websocket
FWIW, Apache 2.4 in CentOS 7.1 has this bug therefore rewrite won't recognize ws:// protocol, and prepends the domain before sending the subrequest. You can test yourself by changing the [P]roxy flag to [R]edirect.charter panorama
Last edited by panoramacharter; 10-05-2021 at 05:13 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
