GetPathInfo () always return String.Empty about hyperfastcgi HOT 5 CLOSED

see #7

from hyperfastcgi.

That was commented out due to these settings
http://mono-project.com/FastCGI_Nginx

fastcgi_param  PATH_INFO          "";
fastcgi_param  SCRIPT_FILENAME    $document_root$fastcgi_script_name;

So PATH_INFO is required to be set to empty string. If you have a test case, which shows that setting path info to empty string is incorrent, I'll change it back.

from hyperfastcgi.

hi @xplicit,
These settings are exemples, and i'm affirmative that PATH_INFO is working with fastcgi-mono-server
My patch in #7 is fixing it for me.
For a small test case you'll have to wait until monday

from hyperfastcgi.

You're right. I was confused by empty PATH_INFO string in fastcgi_params and missed that PATH_INFO is set in other bunch of code. Could you share, how did you configure nginx fastcgi_param to make the patch working for you?

I checked how PATH_INFO worked for xsp (it uses same algorithm as fastcgi-mono-server), and got results:

page: Default.aspx
request: /Default.aspx/test
Request.PathInfo: /test

HttpHandler: <add verb="" path=".sample" type="HelloWorldHandler"/>
request: /123.sample/test
Request.PathInfo: /test

request: /123.sample/123.sample/test
Request.PathInfo: /test

HttpHandler: <add verb="" path="hello" type="HelloWorldHandler"/>
request: /hello/test
Request.PathInfo: (empty string)

looking very strange. Very intresting, how it works on IIS.

from hyperfastcgi.

Hi @xplicit
Here is an extract of my nginx conf

include fastcgi_params;
fastcgi_index PageLogin.aspx;
fastcgi_split_path_info ^((?U).+\.as.x)(/?.+)$;
fastcgi_param PATH_INFO $fastcgi_path_info;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

from hyperfastcgi.