Re: turn off warning message on nginx

On Feb 9, 2011 1:31 PM, “Michael S.” [email protected] wrote:

I think Jerome was working on a fastcgi_param method to alter ini
directives from the nginx conf. IIRC.

Is it available? If not then it won’t help him now. If so, please
enlighten
us.

On Feb 9, 2011, at 7:54 AM, Piotr K. [email protected] wrote:

On 02/04/2011 05:30 PM, lifeisjustabout wrote:

Hi,

Is there any command that i put in conf file to turnoff warning message
of joomla.

for instance in apache .htaccess if i add php_flag display_errors “0”
it

doesnt show me error message anymore

how can i get rid of this problem

thanks in advance

This is php ‘thing’, nginx have nothing to do with it.

Exactly. Have you tried a Google search for “turning off PHP warnings”?
I’m
sure you that you will find what you need without posting here. People
will
be more likely to try to help you if you’ve already tried to help
yourself.

It would be in mail archives somewhere. Either here or on the php-fpm
list. No clue on status or if it ever was done or will be done. I’m not
in a position to google things right now. For all I know it was just a
spitball idea.

2011/2/9 Michael S. [email protected]:

I think Jerome was working on a fastcgi_param method to alter ini
directives from the nginx conf. IIRC.

PHP_VALUE and PHP_ADMIN_VALUE are recognized fastcgi_param keys.

You can set only once each key (only the last will be recognized). So
you have to concatenate the values:

fastcgi_param PHP_VALUE [email protected];

or

fastcgi_param PHP_VALUE “[email protected]
precision=42”;

or

fastcgi_param PHP_VALUE “[email protected] \n
precision=42”;

You can try and make feedbacks !

When was this implemented? What version of fpm would help.

Revision 298383, on Fri Apr 23 16:05:52 2010 UTC. see bug 51595

2011/2/9 Michael S. [email protected]:

2011/2/9 Jérôme Loyet [email protected]:

Revision 298383, on Fri Apr 23 16:05:52 2010 UTC. see bug 51595

Is it in a specific PHP version (5.3.3, 5.3.4, 5.3.5)? Sorry if I’m
not savvy parsing through the logs to determine when it got committed.
I’d like to blog about this so more people know about it (including
myself :))

PHP_ADMIN_VALUE technically allows any PHP_INI_SYSTEM overrides as
well so in theory any ini value can be altered between
PHP_ADMIN_VALUE and PHP_VALUE right?

(at that point I don’t see the need to differentiate really - why
differentiate between admin and user ini values at the webserver
level…)

Would it be possible to make an array style mechanism like:

fastcgi_param PHP_INI_OVERRIDE[] foo=bar;
fastcgi_param PHP_INI_OVERRIDE[] “open_basedir=/var/www/htdocs”;
fastcgi_param PHP_INI_OVERRIDE[] “pcre.backtrack_limit=424242”;

(I don’t know if nginx has this capability or not, but could make it a
bit easier to configure)

$.02

2011/2/9 Michael S. [email protected]:

2011/2/9 Jrme L. [email protected]:

Revision 298383, on Fri Apr 23 16:05:52 2010 UTC. see bug 51595

Is it in a specific PHP version (5.3.3, 5.3.4, 5.3.5)? Sorry if I’m
not savvy parsing through the logs to determine when it got committed.
I’d like to blog about this so more people know about it (including
myself :))

since the first PHP FPM official version as it’s been commited in
april. CQFD

PHP_ADMIN_VALUE technically allows any PHP_INI_SYSTEM overrides as
well so in theory any ini value can be altered between
PHP_ADMIN_VALUE and PHP_VALUE right?

(at that point I don’t see the need to differentiate really - why
differentiate between admin and user ini values at the webserver
level…)

for the same reasons they both exist on apache module (SYSTEM -->
don’t let ini_set() function to change the value, USER --> to let
ini_set() to change the value)

Would it be possible to make an array style mechanism like:

fastcgi_param PHP_INI_OVERRIDE[] foo=bar;
fastcgi_param PHP_INI_OVERRIDE[] “open_basedir=/var/www/htdocs”;
fastcgi_param PHP_INI_OVERRIDE[] “pcre.backtrack_limit=424242”;

(I don’t know if nginx has this capability or not, but could make it a
bit easier to configure)

It’s not possible. It’s a limitation on the fastcgi protocol which
admit each keys only once. (or I missed something)

On Feb 9, 2011, at 12:35 PM, Jérôme Loyet [email protected] wrote:

for the same reasons they both exist on apache module (SYSTEM -->

don’t let ini_set() function to change the value, USER --> to let
ini_set() to change the value

Ah. So if I define as admin it wont let the user override at all. I
thought that was keyed in to the ini level, not the users ability to
override it. Thanks.

It’s not possible. It’s a limitation on the fastcgi protocol which
admit each keys only once. (or I missed something)

In theory it could be scrubbed though by nginx to fold it into a legit
fastcgi param and not require the admin to define it in a funky way. But
that requires some nginx magic too :slight_smile:

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs