Re: Why to have owner's uid of the file when WWW-Authenticate header?
| From: | Uwe Schindler | Date: | Wed, 22 Sep 2004 21:26:28 +0000 |
| Subject: | Re: Why to have owner's uid of the file when WWW-Authenticate header? | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-12941@lists.php.net to get a copy of this message | ||
Something additional to this:
I am fixing bug #29805 (HTTP Authentication Issues in NSAPI).
Copied from some other SAPIs I have done this by adding of the following line:
if (!PG(safe_mode)) php_handle_auth_data(pblock_findval("authorization", rq->headers) TSRMLS_CC);
The problem is: Apache disables this in safe mode only if some other authentication (like .htaccess) is active. In NSAPI you cannot check this, so I disabled the whole authentication in NSAPI. Other SAPIs do not check for safe mode.
What is the background of disabling of passing the headers "Authentication" and the user/password pairs in it to the user? Is it a problem to simply give the user access to this information (even with safe mode) - If there is some authentication by .htaccess or something other it is normally from the same user that wrote the script.
Uwe
At 16:34 22.09.2004, you wrote:
Hi All, I want to know the reason behind the having the uid of the owner of the file shown as a part of realm string the WWW-Authenticate when safe_mode is enabled. With regards Kamesh Jayachandran -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php----- Uwe Schindler thetaphi@php.net - http://www.php.net NSAPI SAPI developer Erlangen, Germany