>For now, to work around the issue, CentOS forum user sercan has provided
the following commands to create
>a new SELinux policy for Nginx. I've tested it on two of my servers and it
works.
> . . .
And there's one more quick workaround to get running very quickly. Not
entirely recommended since
I've verified that the update to Centos 6.6 does indeed relabel nginx
related directories/files during yum update. And a restart of the nginx
process will now have the label "httpd_t". Someone in RH decided to make the
nginx webserver follow the same SELinux policy rules as Apache.
OK, that works
Hello!
> "spdycat" converts all headers to lowercase before send it over SPDY.
Oh, I had not notice it. Thanks(I assumed that nginx converts)
> But the question is why do you care? It seems if you care
> about it, you're definitely doing something wrong.
Maybe so. Sorry for confusion.
Thanks
On Saturday 01 November 2014 10:06:53 cubicdaiya wrote:
> Hello!
>
> I have a question about the behavior of proxing SPDY to HTTP with nginx.
>
[..]
> # spdycat is a command like curl for SPDY.
> # https://github.com/tatsuhiro-t/spdylay
> spdycat \
>--spdy3-1 \
>-H "User-Agent: spdycat" \
Hello!
I have a question about the behavior of proxing SPDY to HTTP with nginx.
First, there is a configuration like the following.
upstream app {
server 127.0.0.1:80;
keepalive 32;
}
server {
listen 443 ssl spdy;
server_name example.com;
pro
