-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Did you try my patch?
On 8/30/2014 09:57, nginxfanboy wrote:
> So now i have one config file with Content. /etc/nginx/nginx.conf
>
> http://paste.debian.net/118297/
>
> Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,252951,252955#ms
So now i have one config file with Content.
/etc/nginx/nginx.conf
http://paste.debian.net/118297/
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,252951,252955#msg-252955
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Yes of course your http configuration works fine because of this
configuration :
location ~ .php$ {
fastcgi_split_path_info ^(.+.php)(/.+)$;
# fastcgi_pass 127.0.0.1:9000;
fastcgi_pass unix:/
I'm using FPM and it works with my normal Config.
See here :)
http://paste.debian.net/118317/
http://image-upload.de/image/IwopSE/779b6e16ae.png
I believe it's work because of the insanity of my two config files xD.
/etc/nginx/sites-available/defaulthttp://paste.debian.net/118318/
or
/etc/n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Your configuration looks like uncomplete, are you using fpm or httpd
as reverse proxy? This line shows your php was un-processed.
... snip ...
location / {
root /usr/share/nginx/www;
index index.php index.html;
}
When i open my Website with https:// I become a Download with a Binary file
:-(
In the Binary File is my Website xD. The Certificate are accept by my
Browser but it don't work. Also I become a 404 Message and a Download >.<
My /etc/nginx/nginx.conf http://paste.debian.net/118297/
I'm using Debi
Hello,
I am receiving "upstream timed out (110: Connection timed out) while
connecting to upstream, client" errors. They are comet calls and I wonder if
increasing the proxy_connect_timeout will help. i have increased
proxy_send_timeout and proxy_read_timeout to 6000 and have turned off
proxy_buf
Hello!
On Fri, Aug 29, 2014 at 11:55:08AM -0400, gthb wrote:
> Hi,
>
> is it possible to hide one request cookie (but not all, so proxy_set_header
> Cookie "" is not the way) when proxying to an upstream server?
>
> The use case is:
>
> * website foo.com uses a hosted service on a subdomain, e
This patch adds two features:
mp4_limit_rate 1.1; # multiplied by average bitrage
mp4_limit_rate_after 15s; # time
http://doppelbauer.name/nginx-1.6.1-mp4_limit_rate.patch
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,252946,252946#msg-252946
_
Hi,
is it possible to hide one request cookie (but not all, so proxy_set_header
Cookie "" is not the way) when proxying to an upstream server?
The use case is:
* website foo.com uses a hosted service on a subdomain, e.g. blog.foo.com
hosted by Wordpress.com
* horror: MSIE will send all foo.com
Hello Maxim,
I tried enabling debug mode but still I am not able to figure out the issue
and its possible solutions.
I disabled this rewrites which are rewriting to index.html
## Rewrite all directory lookups to 'index.html'
#rewrite ^(.*)/$ $1/index.html permanent;
## Rewrite all open strings
11 matches
Mail list logo