We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
qiita/qiita_pet/nginx_example.conf
Lines 59 to 66 in 57d1b14
W 240215 18:58:08 web:2161] 400 GET /study/list/socket/ (127.0.0.1) 4.57ms [D 240215 18:58:08 websocket:164] Can "Upgrade" only to "WebSocket".
Should we add a working configuration to this example, such that user do not have to solve this issue by themselves? Btw. I am not sure what the matching configuration would look like, can we follow: https://www.serverlab.ca/tutorials/linux/web-servers-linux/how-to-configure-nginx-for-websockets/ ?
The text was updated successfully, but these errors were encountered:
Fixed here: #3362
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
qiita/qiita_pet/nginx_example.conf
Lines 59 to 66 in 57d1b14
The provided example nginx configuration seems to not forward websocket HTTP traffic.
Should we add a working configuration to this example, such that user do not have to solve this issue by themselves? Btw. I am not sure what the matching configuration would look like, can we follow: https://www.serverlab.ca/tutorials/linux/web-servers-linux/how-to-configure-nginx-for-websockets/ ?
The text was updated successfully, but these errors were encountered: