Show all posts by user
Discussions in Russian
Page 8 of 8
Pages: 
45678
Results 211 - 226 of 226
Валентин Бартенев Wrote:
-------------------------------------------------------
> On Tuesday 12 July 2011 18:11:55 locojohn wrote:
> > fastcgi_pass PHP_VALUE
> >
> "include_path=\${include_path}:/my/other/include/p
> ath";
> >
> > Может ли nginx пропускать
> символ доллара
> > "$"
by
locojohn
-
Nginx Mailing List - Russian
> Hmm, never tried that, using a variable. Don't
> know if the $ needs to
> be escaped.
>
> You'll have to try it.
Of course I tried both:
fastcgi_param PHP_VALUE "include_path=${include_path}:/my/other/path";
and
fastcgi_param PHP_VALUE "include_path=\${include_path}:/my/other/path";
and neither works, hence I wrote here.
Andrejs
by
locojohn
-
Nginx Mailing List - English
Уважаемые коллеги,
Как известно, на данный момент возможна передача PHP_INI* параметров в связке с PHP-FPM через fastcgi_param PHP_VALUE и fastcgi_param PHP_ADMIN_VALUE.
Но как использовать уже существующие значения параметров конфигурации PHP при
by
locojohn
-
Nginx Mailing List - Russian
hobson42 Wrote:
> > Igor, how about using the current values of
> PHP_INI* variables inside
> > the definition e.g.:
> >
> >
> This is impossible. Think about what nginx does -
> It matches filenames
> to a mask and passes the request using CGI to the
> port defined on a match.
>
> There is no reason why Nginx should know the CGI
> se
by
locojohn
-
Nginx Mailing List - English
Igor Sysoev Wrote:
-------------------------------------------------------
> 12.07.2011, в 13:19, "locojohn"
> <nginx-forum@nginx.us> написал(а):
> > # fix compatible SCRIPT_URL/SCRIPT_URI variables
> > if ($request_uri ~ ^([^?]+)) {
> > set $script_url $1;
> > }
>
> Если я правильно понимаю
>
by
locojohn
-
Nginx Mailing List - Russian
Игорь, но что, если мне кроме PATH_INFO нужно и SCRIPT_URL/SCRIPT_URI правильные поставить, не url-encoded? Дело в том, что SCRIPT_URL/SCRIPT_URI, для совместимости со старыми скриптами, опирающимися на конфигурацию для Apache, не должны содержать имя ис
by
locojohn
-
Nginx Mailing List - Russian
Игорь, я разобрался. В SiteSupra CMS присутсвовали хитрые rewrite и нужно было переделать конфигурацию, чтобы location с кэпчурингом срабатывал. Большое вам спасибо!
Андрей
by
locojohn
-
Nginx Mailing List - Russian
Denis F. Latypoff Wrote:
-------------------------------------------------------
> > Как именно получается
> PATH_INFO ? Если rewrite/set,
> > то кодируется. Нужно так:
> >
> - location ~ \.php(<?PATH_INFO>/.+)$ {
> + location ~ \.php(?<PATH_INFO>/.+)$ {
> > ...
> - fastcgi
by
locojohn
-
Nginx Mailing List - Russian
Igor Sysoev Wrote:
-------------------------------------------------------
> On Fri, Jun 18, 2010 at 08:23:16AM -0400, jbruni
> wrote:
>
> > UPDATE
> >
> > Now, it is possible to do this way:
> >
> >
> > fastcgi_param PHP_VALUE
> "upload_max_filesize=5M";
> >
> >
> > More information here:
> >
by
locojohn
-
Nginx Mailing List - English
Увы, cgi.fix_pathinfo=1 уже стоит в php.ini. И это не меняет дело. Дело в том, что, похоже, директива fastcgi_param автоматически url-енкодирует передаваемые строки в окружение. Например:
set $test $uri;
fastcgi_param TEST $test;
если оригинальный $request_uri
by
locojohn
-
Nginx Mailing List - Russian
Sergey Shepelev Wrote:
> Вообще-то перейти с апача
> на nginx можно только в том
> случае, если там
> апач использовался для
> раздачи статики и
> проксирования на бекенды.
> Это
> очень редкая ситуация, чаще
> всего в а
by
locojohn
-
Nginx Mailing List - Russian
Дорогие форумчане!
Одна из проблем, с которой я столкнулся при переводе всех наших сайтов с Apache под nginx - это установка правильных путей в PATH_INFO. Дело в том, что согласно спецификации CGI 1.1, PATH_INFO должен содержать url-decoded с
by
locojohn
-
Nginx Mailing List - Russian
In my case problem was solved, as it was incorrect rewrite rule and the PHP script never received control, hence - 405. May I suggest that all who receive 405 responses first check whether rewrite rules are correctly configured.
Andrejs
by
locojohn
-
Nginx Mailing List - English
Dear Igor,
According to my understanding, either way PATH_INFO is set to url-encoded string, while according to CGI 1.1 specification, it should contain the url-decoded string. Which brings troubles when there are spaces in file names, for instance.
I am using nginx 1.0.4 and this still seems like an issue. Is there a way to pass url-decoded strings over to fastcgi applications?
Thank y
by
locojohn
-
Nginx Mailing List - English
Dear forum members and nginx developers,
I am running nginx 1.0.4 with php 5.3.6 on the linux server. Some older sites that we host require PATH_INFO to be set correctly. In certain cases, due to fairly complex rewrite rules required by the older CMS to work, we cannot set PATH_INFO using fastcgi_split_path_info (and also due to the fact that the infamous exploit exists: /uploads/evilimage.jp
by
locojohn
-
Migration from Other Servers
Unfortunately, I too am getting the 405 response from the SiteSupra CMS management system when running in the admin mode:
"POST /index.php/supra/block/en/scale.php?SCALE/16100 HTTP/1.1" 405 754
However, this is a PHP script, so why does it give the 405 status?
Many thanks for suggestions
Andrejs
by
locojohn
-
Nginx Mailing List - English
Page 8 of 8
Pages: 
45678