Roger,

I found I had to run two levels of security as htdig knows only about 
.htaccess type. So I faked it out, as follows:
<? session_start();
if( $HTTP_SERVER_VARS[ "PHP_AUTH_USER" ] !="prince" && $HTTP_SERVER_VARS[ 
"PHP_AUTH_PW" ] !="charming" )
{
if( !session_is_registered( "member_id" ) )
{
header("Location: user_logon.php\n");
}
}?>

I have nothing in .htacces, "prince" and "charming" are supplied as valid 
paswords in the htdig script. This enables htdig to jump over the next if, 
which is where the normal user is validated against a database in the 
user_logon.php script. Before I added this outer if htdig was always 
getting a redirect to user_logon.

htdig is run from a php script, called as follows:
system( "./htdig -i -v -u prince:charming " )

Hope this helps - Miles

At 04:27 PM 5/29/01 -0700, Harrell, Roger wrote:
>I recently implemented htdig et al.
>
>I have need to set up an htdig configuration that can send vars with each
>request. I have a password protected area of the site that uses PHP sessions
>and I would like that area searchable. The way it's set up I can bypass the
>sessions if the proper variables are sent with each request but the only
>thing I've seen for htdig is to send the standard http user and password,
>not custom vars. Any way to do this??
>
>Thanks,
>Roger Harrell
>
>_______________________________________________
>htdig-general mailing list <[EMAIL PROTECTED]>
>To unsubscribe, send a message to 
><[EMAIL PROTECTED]> with a subject of unsubscribe
>FAQ: http://htdig.sourceforge.net/FAQ.html


_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a 
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html

Reply via email to