2009/6/19 Igor Sysoev

> On Fri, Jun 19, 2009 at 07:59:55AM -0700, Kevin Castiglione wrote:
>
> > On Fri, Jun 19, 2009 at 7:48 AM, Edho P Arief
> wrote:
> >
> > > On Fri, Jun 19, 2009 at 9:28 PM, Kevin
> > > Castiglione wrote:
> > > > 2009/6/19 Igor Sysoev
> > > >>
> > > >> On Fri, Jun 19, 2009 at 05:54:06AM -0700, Kevin Castiglione wrote:
> > > >>
> > > >> > > Probably, you need
> > > >> > >
> > > >> > > fastcgi_param SCRIPT_FILENAME
> > > >> > > /home/app/work/flock/$host$fastcgi_script_name;
> > > >> > >
> > > >> > > or
> > > >> > >
> > > >> > > fastcgi_param SCRIPT_FILENAME
> > > >> > > $document_root/$host$fastcgi_script_name;
> > > >> > >
> > > >> > tried these with no results igor!
> > > >>
> > > >> What server did you use before nginx ?
> > > >
> > > > ive always used nginx. this is a new setup im trying to do.
> > > > thank you
> > > >
> > > >
> > >
> > > how's the old setup looks like?
> >
> >
> > the config for the current setup is given below. i have different domains
> > setup with different server blocks. i want to combine them to one fastcgi
> > backend, and my webframe work supports only url level - sub application
> > processing. hence i need the url mapping.
>
> So now you use differen ports in upstream, say, 8492:
>
> server app1.XXX.com:8492 fail_timeout=1s;
>
> Yes ?

yes, differentports



>
> With this configuraiton
>
> fastcgi_param SCRIPT_FILENAME $fastcgi_script_name;
> fastcgi_param PATH_INFO $fastcgi_script_name;
>
> both SCRIPT_FILENAME and PATH_INFO are equal to URI, i.e., if client
> requests "/some/page", then these parameter will be "/some/page" too.
>
> Probably, you need
>
> fastcgi_param SCRIPT_FILENAME /$host$fastcgi_script_name;
> fastcgi_param PATH_INFO /$host$fastcgi_script_name;
>
> finally got it working
these are the changes i had to do

fastcgi_param SCRIPT_NAME $host$fastcgi_script_name;
fastcgi_param SCRIPT_FILENAME /$host$fastcgi_script_name;
fastcgi_param PATH_INFO /$host$fastcgi_script_name;


thanks a lot igor and edho!