NginX problem with Reverse Proxy'ing

[Victor Fondevilla]

Finally I reinstalled everything and it worked flawlessly.

-----Original Message-----
From: Maxim Dounin [mailto:mdounin at mdounin.ru] 
Sent: domingo, 11 de abril de 2010 16:46
To: nginx at nginx.org
Subject: Re: NginX problem with Reverse Proxy'ing

Hello!

On Sun, Apr 11, 2010 at 03:15:22PM +0200, Victor Fondevilla wrote:

> I just restarted Nginx and Apache renaming log files to have fresh ones.
> Here are the snips from log:
> 
> Nginx Access Log
> 83.97.217.199 - - [11/Apr/2010:12:41:51 +0000] "GET /index.php HTTP/1.1"
301
> 20 "-" "Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0;
> SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media
> Center PC 6.0; InfoPath.2; Tablet PC 2.0)"
> 
> Apache Access Log
> 127.0.0.1 - - [11/Apr/2010:12:41:51 +0000] "GET /index.php HTTP/1.0" 301
376
> "-" "Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0;
SLCC2;
> .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center
PC
> 6.0; InfoPath.2; Tablet PC 2.0)"

So it's obviously Apache which retruned 301.  You have to dig into 
your Apache configuration and/or your php code to find out what's 
happening.

> There isn't nothing in apache or nginx error logs.
> 
> I double-checked the index.php file and is in the correct path /var/www/

Hint: start from checking if it's in fact called, most likely it's 
not.  Either due to rewrites you configured in Apache config 
and/or .htaccess, or due to some other Apache configuration 
options.

Maxim Dounin

_______________________________________________
nginx mailing list
nginx at nginx.org
http://nginx.org/mailman/listinfo/nginx
No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.801 / Virus Database: 271.1.1/2789 - Release Date: 04/10/10
20:32:00