Show all posts by user
Anything related to migrating to nginx, including rewrites
Re: Problems with trailing slashes/path_info (php-fpm) - 12 years ago
Actually I was being stupid about it... location ~ ^(?P<script_name>.+\.php)(?P<path_info>/.+)$ { should be location ~ ^(?P<script_name>.+\.php)(?P<path_info>/.*)$ { to allow a /?... Its now working... a bit paranoid about fixpath being 1, so I'm going to look into it all a bit deeper... Thanks for your help though Andrejs, much appreciated!by RVN - How to...
Re: Problems with trailing slashes/path_info (php-fpm) - 12 years ago
fix_pathinfo was 0... It has always been 0 as our app was designed to not rely on that... I've always heard that it was a bad idea? Anyways, with pathinfo=1, it works for script.php/something?param=abc... still doesnt work for script.php/?param=abc... cool... 2 working :) 1 to go... unfortunately this 1 is the one I was seeing popping up in the logs when I put nginx in our test environment... :(by RVN - How to...
Re: Problems with trailing slashes/path_info (php-fpm) - 12 years ago
Sorry about that... I should have checked better about the latest versions... I guess I'll end up building pcre from source... Anyways, trying it with the ?P<xx> format... Seems like I'm closer, but still not quite... Nginx.conf excerpt: location ~ ^(?P<script_name>.+\.php)$ { #try_files $script_name =404; include fastcgi_params; fastcgi_param SCRIPT_FILENAME $document_root$by RVN - How to...
Re: Problems with trailing slashes/path_info (php-fpm) - 12 years ago
I kind of follow your logic on your method, but from wht I read the initial methods *should* have worked too? oh well.. anyways, thanks for your help, but still I'm getting the same error... nginx: pcre_compile() failed: unrecognized character after (?< in "^(?<script_name>.+\.php)$" at "script_name>.+\.php)$" in /etc/nginx/nginx.conf:81 nginx: configurationby RVN - How to...
Re: Problems with trailing slashes/path_info (php-fpm) - 12 years ago
I get a regex error... ---- : pcre_compile() failed: unrecognized character after (?< in "^(?<script_name?>.+\.php)$" at "script_name?>.+\.php)$" in /etc/nginx/nginx.conf:117 configuration file /etc/nginx/nginx.conf test failed ----- I'm not supposed to replace <script_name> with my actual php right? Because there are many variations... I was lookinby RVN - How to...
Re: php_info - fastcgi_split_path_info - Not does not work - 12 years ago
By any chance did you try changing: location ~ ^.+\.php$ { include fastcgi_params; fastcgi_intercept_errors on; fastcgi_pass unix:/tmp/php.socket; } to remove the $ from .php$? so it reads: location ~ ^.+\.php { include fasby RVN - Migration from Other Servers
Problems with trailing slashes/path_info (php-fpm) - 12 years ago
Dear All, I have been having a hell of a time debugging an issue with nginx... The issue is the following, if someone tries to access mysite.com/myscript.php it works, but if for some reason they try accessing myscript.php/?param=ssss (Dont ask me why i'm getting this, i assume its some sort of ill formed ajax somewhere or its nginx that is re-writing something strangely...) If i try acceby RVN - How to...
 |
 |
 |
 |
|