Just create php.exe (CLI version) in Debug_TS\cli, Release_TS\cli and
Release_TS_inline\cli
- Frank
> On Fri, 20 Dec 2002, Frank Kromann wrote:
> > Hi Andrei,
> >
> > Should I commit a small fix to the Windows projects to avoid having
the
> > CGI and CLI produce php.exe to the same directory ?
>
Hi,
> > > Possible values are:
> > >
> > > - php_auth_exposure=user
> > > Only PHP_AUTH_USER is exposed.
> > >
> > > - php_auth_exposure=pw
> > > Only PHP_AUTH_PW is exposed
> > >
> > > - php_auth_exposure=user,pw
> > > Both PHP_AUTH_USER and PHP_AUTH_PW are exposeed
> >
> > Moriyoshi, have
On Sun, 22 Dec 2002, Moriyoshi Koizumi wrote:
>
> Andrei Zmievski <[EMAIL PROTECTED]> wrote:
> > Moriyoshi,
> >
> > I appreciate your effort here, but it seems that while this approach is
> > more flexible, it is also bound to have more complicated. I have decided
^^
On Sat, 21 Dec 2002, Edin Kadribasic wrote:
> Andrei I think that we should include this small change in 4.3.0. It cannot
> possibly affect anything in the negative way and I will make sure that the
> files are correctly placed in the distribution.
Ok, go ahead with this.
-Andrei
Andrei Zmievski <[EMAIL PROTECTED]> wrote:
> Moriyoshi,
>
> I appreciate your effort here, but it seems that while this approach is
> more flexible, it is also bound to have more complicated. I have decided
> to apply Philip's patch for 4.3.0.
I think my patch is too complicated to be included i
> Should I commit a small fix to the Windows projects to avoid having the
> CGI and CLI produce php.exe to the same directory ?
Andrei I think that we should include this small change in 4.3.0. It cannot
possibly affect anything in the negative way and I will make sure that the
files are correctly
Moriyoshi,
I appreciate your effort here, but it seems that while this approach is
more flexible, it is also bound to have more complicated. I have decided
to apply Philip's patch for 4.3.0.
On Sat, 21 Dec 2002, Moriyoshi Koizumi wrote:
> Ohh, it seems we have been working on the same patch simul
On Fri, 20 Dec 2002, Frank Kromann wrote:
> Hi Andrei,
>
> Should I commit a small fix to the Windows projects to avoid having the
> CGI and CLI produce php.exe to the same directory ?
What will the fix do exactly?
-Andrei http://www.gravitonic.com/
"What's
> There is no difference here, both are strings anyway. And the latest
> option "AUTH_EXPOSE_USER | AUTH_EXPOSE_PW" wont work in an httpd.conf
> file. Also, this is NOT the style we have in php.ini. I don't see any
> valid point to use this thing.
Derick,
you may have a point about it not being a
On Sat, 21 Dec 2002, Leon Atkinson wrote:
> > Possible values are:
> >
> > - php_auth_exposure=user
> > Only PHP_AUTH_USER is exposed.
> >
> > - php_auth_exposure=pw
> > Only PHP_AUTH_PW is exposed
> >
> > - php_auth_exposure=user,pw
> > Both PHP_AUTH_USER and PHP_AUTH_PW are exposeed
>
> M
> Possible values are:
>
> - php_auth_exposure=user
> Only PHP_AUTH_USER is exposed.
>
> - php_auth_exposure=pw
> Only PHP_AUTH_PW is exposed
>
> - php_auth_exposure=user,pw
> Both PHP_AUTH_USER and PHP_AUTH_PW are exposeed
Moriyoshi, have you considered using constants here instead of strin
Ohh, it seems we have been working on the same patch simultaneously :)
Attached is my version of fix for bug #20441, which adopts a new ini entry
"php_auth_exposure" so that administrators can selectively expose auth
information to the clients regardless of safe_mode settings.
Possible values a
Attatched is a patch that essentially goes back
to 4.2.3 behavior except the external auth will not
be available with PHP in safe mode. REMOTE_USER
exists regardless.
It seems some people also wanted an ini option, I don't
know how to do that! :)
References for this patch:
http://bugs.php.n
Hi Andrei,
Should I commit a small fix to the Windows projects to avoid having the
CGI and CLI produce php.exe to the same directory ?
- Frank
> Everyone,
>
> I have just released 4.3.0RC4. Despite the quote in my signature, I am
> determined to keep this one the very last final RC of the inter
I'll have a patch in about one hour! :)
Regards,
Philip
On Fri, 20 Dec 2002, Andrei Zmievski wrote:
> Everyone,
>
> I have just released 4.3.0RC4. Despite the quote in my signature, I am
> determined to keep this one the very last final RC of the interminable
> 4.3.0 development cycle. Toward
Everyone,
I have just released 4.3.0RC4. Despite the quote in my signature, I am
determined to keep this one the very last final RC of the interminable
4.3.0 development cycle. Towards that end, I will closely monitor the
CVS commits and revert any that do not satisfactorily explain what
critical
16 matches
Mail list logo