On Thu, 29 Jan 2015, silvioprog wrote:
Hello,
I've the same problem in Apache and nginx: TRequest.PathInfo always returns an
empty string.
In Apache, I'm using the the mod_proxy_fcgi module already distributed in
Apache 24. In nginx, I'm using this configuration:
location /dev/duallsms {
fastcgi_pass localhost:8080;
... other configurations ...
fastcgi_param PATH_INFO $fastcgi_path_info; # from nginx docs
}
First I've tested it on Windows, but I've noticed that it fail in Linux too. So
I ask: is PATH_INFO available in FastCGI (working as proxy)? If not, what I use
instead it?!
PATH_INFO is not always available, you need to configure that in apache and/or
nginx.
See http://httpd.apache.org/docs/trunk/mod/mod_proxy_fcgi.html
The FPC fcl-web components by themselves do not try to reconstruct PATH_INFO.
You can try determining it from SCRIPT_URI or SCRIPT_NAME.
Michael.
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
