Hello!
On Tue, Feb 25, 2014 at 01:05:44AM +0100, B.R. wrote:
> Hello Francis and Maxim,
>
> I understand very well that $fastcgi_script_name value is defined after
> fastcgi_split_path_info is called.
> However I was wondering about other variables which value depend on
> $fastcgi_script_name, f
Hello Francis and Maxim,
I understand very well that $fastcgi_script_name value is defined after
fastcgi_split_path_info is called.
However I was wondering about other variables which value depend on
$fastcgi_script_name, for example when PHP's SCRIPT_NAME has been defined
in the already included
On 2014.02.23. 14:51, Maxim Dounin wrote:
> Try this:
>
> fastcgi_param SCRIPT_FILENAME "$document_root$fastcgi_script_name";
>
> or this:
>
> fastcgi_param SCRIPT_FILENAME '$document_root$fastcgi_script_name';
>
> If a parameter includes special characters, the whole parameter
> should
Hello!
On Mon, Feb 24, 2014 at 11:39:39PM +0100, B.R. wrote:
> Hello,
>
> I am considering the following configuration:
> server {
> include fastcgi.conf # Default configuration coming with a Debian
> package which contains a definition of the SCRIPT_FILENAME FastCGI variable
> with $documen
On Mon, Feb 24, 2014 at 11:39:39PM +0100, B.R. wrote:
Hi there,
> server {
> include fastcgi.conf # Default configuration coming with a Debian
> ...
> location ~^/index\.php {
> fastcgi_split_path_info ^(/index\.php)(/.*)$;
> }
> Will the FastCGI SCRIPT_FILENAME variable valu
Hello,
I am considering the following configuration:
server {
include fastcgi.conf # Default configuration coming with a Debian
package which contains a definition of the SCRIPT_FILENAME FastCGI variable
with $document_root$fastcgi_script_name as its value
...
location ~^/index\.php {
useopenid Wrote:
---
> I am looking at proxying to google as well, and thus need SSL on the
> backside (and would like it on general principles for other cases as
> well)
Here you go: http://forum.nginx.org/read.php?2,219069,247910#msg-247910
Po
Now, here is the minimal patch:
https://raw.github.com/druga/aeriebsd-tree/master/usr.sbin/nginx/patch-nginx_mail_proxy_ssl_backends.diff
I do provide neither hostnames nor starttls support in it, because the code
for their support is too much invasive :-(
P.S.: The patch isn't good enough to be i
> location /mailadmin/(.*.\.php)${
This should probably be:
location ~ /mailadmin/(.*\.php)$ {
Otherwise it's not treated as regex.
On Monday, February 24, 2014 04:01:03 PM basti wrote:
> Hello,
> I have a SSL config like
>
> server {
>
> server_name ...;
>
> # do not rewrite this
> locat
On Mon, Feb 24, 2014 at 04:10:24PM +0100, basti wrote:
Hi there,
> # do not rewrite this
> location /mailadmin/(.*.\.php)$ {
You probably will have no requests that will match this prefix location.
> location / {
> rewrite ^ http://$server_name$request_uri? permanent;
Many requests wi
Sorry same result.
On 24.02.2014 16:34, Styopa Semenukha wrote:
> Use:
> return 301 http://$server_name$request_uri;
> to redirect.
>
> On Monday, February 24, 2014 04:01:03 PM basti wrote:
>> Hello,
>> I have a SSL config like
>>
>> server {
>>
>> server_name ...;
>>
>> # do not rewrite this
>
> The message indicate that upstream server returned invalid
> response, or at least nginx thinks it is invalid. If you think
> that response returned is valid, it's good idea to actually
> provide what was returned, as well as nginx's debug log.
>
>
> --
> Maxim Dounin
> http://nginx.org/
Tha
On Mon, Feb 24, 2014 at 5:21 PM, Louis Cordier wrote:
> When I connect to production.example.com/static/ I get served the files
> from capture.example.com/static/.
>
You can ignore this part, looks like browser caching.
___
nginx mailing list
nginx@ngi
Use:
return 301 http://$server_name$request_uri;
to redirect.
On Monday, February 24, 2014 04:01:03 PM basti wrote:
> Hello,
> I have a SSL config like
>
> server {
>
> server_name ...;
>
> # do not rewrite this
> location /mailadmin/(.*.\.php)${
>...
># some stuff
> }
>
>
>
I am using nginx/1.1.19 (Ubuntu 12.04.3).
I have 3 reverse proxies setup, like so:
server {
listen 80;
server_name ebatch.example.com;
client_max_body_size 20m;
location / {
proxy_pass http://127.0.0.1:8000/;
include /etc/nginx/proxy.conf;
}
location /st
Hello,
I have a config like:
server {
...
# do not rewrite this
location /mailadmin/(.*.\.php)$ {
# some stuff
}
location / {
# some other stuff
rewrite ^ http://$server_name$request_uri? permanent;
}
location ~ \.php$ {
# php stuff;
}
}
URLs like
htt
Hello,
I have a SSL config like
server {
server_name ...;
# do not rewrite this
location /mailadmin/(.*.\.php)${
...
# some stuff
}
location / {
...
rewrite ^ http://$server_name$request_uri? permanent;
}
location ~ \.php$ {
...
# php stuff
}
}
URLS like
https:
Hello!
On Mon, Feb 24, 2014 at 09:04:07AM -0500, nginx user wrote:
> I have seen errors in my logs: worker_connections are not enough while
> requesting certificate status
>
> I believe the main problem was that the worker_connections was set too low,
> and I've fixed that.
>
> However after lo
I got it!
SPDY breaks as soon as my Upstream uses GZip! I turned GZip off in Railo and
voila it works. Turn it on and get blank page again.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,247692,247893#msg-247893
___
nginx mailing list
nginx@
I have seen errors in my logs: worker_connections are not enough while
requesting certificate status
I believe the main problem was that the worker_connections was set too low,
and I've fixed that.
However after looking at the source around the OCSP stapling, I have a
couple questions:
- It appe
Hello,
The debug log is huge. Any ideas where to uploaded?
BR/Kostas
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,247886,247891#msg-247891
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello!
On Mon, Feb 24, 2014 at 06:34:41AM -0500, greekduke wrote:
> Hello,
>
> Hello,
>
> I have an issue with segfaults especially when I send lot's of traffic to
> the server. The hardware is an HP proliant G8 with 24 cores but I am using
> only one worker because the problem becames worse wi
Hello,
Hello,
I have an issue with segfaults especially when I send lot's of traffic to
the server. The hardware is an HP proliant G8 with 24 cores but I am using
only one worker because the problem becames worse with more than one. I have
also modified the ulimit for the nginx user up to 65535 b
Hello!
On Mon, Feb 24, 2014 at 11:52:48AM +0100, Wim R. Crols wrote:
> Hi,
>
> We are using nginx as a reverse proxy before JBoss and Apache. Certain POST
> requests are failing when passing through nginx. /var/log/nginx/error.log
> showed errors like this:
>
> 2014/02/24 10:05:05 [error] 3409#
Hi,
We are using nginx as a reverse proxy before JBoss and Apache. Certain POST
requests are failing when passing through nginx. /var/log/nginx/error.log
showed errors like this:
2014/02/24 10:05:05 [error] 3409#0: *1744 upstream sent invalid chunked
response while reading response header from up
25 matches
Mail list logo
