Hello,guys!
How I can set Sec-WebSocket-Protocol in config?
I've tried proxy_set_header Sec-WebSocket-Protocol "v10.stomp, v11.stomp";
and add_header Sec-WebSocket-Protocol "v10.stomp, v11.stomp".
In response, I'm not getting 'Sec-WebSocket-Protocol' header.
What can be wrong?
P.S. Nginx 1.6.2
B
Thank you, Francis, for your answer.
The question is more metaphysical, actually, —
why the module what declares that it "implements client authorization based on
the result of a subrequest"
does not allow to use direct external URI as value for the address of this
"sbrequest"; and the subrequest
Hello Jeff,
Thank you for your help. I tested your suggestion. This isn't the case. I
also tested in normal debian system and this wasn't the case there either.
I believe following section is the culprit. Start-stop-daemon tests if
daemon was already running, however it doesn't relinquish the s
anyone, please?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,272281,272590#msg-272590
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
For a server {} that you want to make both universally compatible with both
http port 80 and https port 443 ssl requests.
This was my solution for my own sites.
#inside http block
upstream proxy_web_rack { #port 80 unsecured requests
server 172.16.0.1:80;
}
upstream proxy_web_rack_ssl { #port 443
I suggest splitting your upstreams by protocol, then proxying requests
depending on HTTPS headers to the apropriate group. There's an example on
how to detect HTTPs at
http://serverfault.com/questions/527780/nginx-detect-https-connection-using-a-header
On Thu, Feb 23, 2017 at 4:38 AM, Kilian Ries
I think i already tried what you suggested, but that doesn't work because i
have to set a specific protocol in the proxy_pass command (http or https). If i
have a mixed upstream group like
upstream proxy_backend {
server xxx.xx.188.53;
server xxx.xx.188.53:443;
}
i always get
