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

Websocket endpoint and ProxyFixMiddleware #198

Open
hhakk opened this issue Feb 28, 2024 · 1 comment
Open

Websocket endpoint and ProxyFixMiddleware #198

hhakk opened this issue Feb 28, 2024 · 1 comment

Comments

@hhakk
Copy link

hhakk commented Feb 28, 2024

I deployed a Quart app on Azure (using Docker), and they have some kind of reverse proxy that decrypts HTTPS traffic to HTTP traffic.

Now if I apply ProxyFixMiddleware and use url_for(<websocket-endpoint>) in my template, I correctly get a wss address rendered BUT Quart always responds with HTTP 400.

If I do not apply the middleware and manually set the protocol to wss on the template, I can succesfully establish a websocket connection. Why is this?

Using quart = 0.19.4 and hypercorn = 0.16.0

@pgjones
Copy link
Owner

pgjones commented May 28, 2024

Does the url_for result differ in the two circumstances? If so could you share the values

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

2 participants