On 27 Aug 2013, at 18:45, Jim Giner wrote:
> From your latest missive I gleaned that I needed to have a script on my server
One last time: YOU DON'T NEED TO CHANGE ANYTHING ON THE SERVER-SIDE!
Ok, I see that you've decided to use another method, which is great; HTTP auth
is a pretty antiquated
Stuart,
Just wanted to follow up with my thanks for your excellent help in
providing understanding of how to generate the 401 error page and
getting me thru the process of performing a sign-out from basic auth.
Without your patience it never would have happened.
Also wanted to tell you that
On 8/27/2013 12:53 PM, Stuart Dallas wrote:
On 27 Aug 2013, at 17:28, Jim Giner wrote:
On 8/27/2013 11:56 AM, Stuart Dallas wrote:
Oops, sent this message from the wrong email address, so the list rejected it.
Begin forwarded message:
From: Stuart Dallas
Subject: Re: [PHP] Basic Auth
On 27 Aug 2013, at 17:28, Jim Giner wrote:
> On 8/27/2013 11:56 AM, Stuart Dallas wrote:
>> Oops, sent this message from the wrong email address, so the list rejected
>> it.
>>
>> Begin forwarded message:
>>
>>> From: Stuart Dallas
>>> Sub
On 8/27/2013 11:56 AM, Stuart Dallas wrote:
Oops, sent this message from the wrong email address, so the list rejected it.
Begin forwarded message:
From: Stuart Dallas
Subject: Re: [PHP] Basic Auth
Date: 27 August 2013 16:36:27 BST
To: jim.gi...@albanyhandball.com
Cc: php-general
Oops, sent this message from the wrong email address, so the list rejected it.
Begin forwarded message:
> From: Stuart Dallas
> Subject: Re: [PHP] Basic Auth
> Date: 27 August 2013 16:36:27 BST
> To: jim.gi...@albanyhandball.com
> Cc: php-general@lists.php.net
>
> On 27 Au
On 8/27/2013 10:55 AM, Stuart Dallas wrote:
On 27 Aug 2013, at 15:51, Jim Giner wrote:
On 8/27/2013 10:39 AM, Stuart Dallas wrote:
On 27 Aug 2013, at 15:18, Jim Giner wrote:
On 8/27/2013 10:14 AM, Stuart Dallas wrote:
It's not really confusing so long as you understand how PHP works. Eac
On 27 Aug 2013, at 15:51, Jim Giner wrote:
> On 8/27/2013 10:39 AM, Stuart Dallas wrote:
>> On 27 Aug 2013, at 15:18, Jim Giner wrote:
>>
>>> On 8/27/2013 10:14 AM, Stuart Dallas wrote:
It's not really confusing so long as you understand how PHP works. Each
request is brand new - not
On 8/27/2013 10:39 AM, Stuart Dallas wrote:
On 27 Aug 2013, at 15:18, Jim Giner wrote:
On 8/27/2013 10:14 AM, Stuart Dallas wrote:
It's not really confusing so long as you understand how PHP works. Each request
is brand new - nothing is retained from previous requests. The two variable
you
On 27 Aug 2013, at 15:18, Jim Giner wrote:
> On 8/27/2013 10:14 AM, Stuart Dallas wrote:
>> It's not really confusing so long as you understand how PHP works. Each
>> request is brand new - nothing is retained from previous requests. The two
>> variable you're changing are set by PHP when the r
On 8/27/2013 10:14 AM, Stuart Dallas wrote:
It's not really confusing so long as you understand how PHP works. Each request
is brand new - nothing is retained from previous requests. The two variable
you're changing are set by PHP when the request comes in from the browser. The
fact you chang
On 27 Aug 2013, at 15:06, Jim Giner wrote:
>
> On 8/27/2013 9:46 AM, Stuart Dallas wrote:
>> On 27 Aug 2013, at 14:37, Jim Giner wrote:
>>
>>> I"m using basic auth for a few of my pages that I want to limit access to -
>>> nothing of a sensitive nature, but simply want to limit access to. Wa
On 8/27/2013 9:46 AM, Stuart Dallas wrote:
On 27 Aug 2013, at 14:37, Jim Giner wrote:
I"m using basic auth for a few of my pages that I want to limit access to -
nothing of a sensitive nature, but simply want to limit access to. Want to
implement a signoff process, but can't figure it out.
On 27 Aug 2013, at 14:37, Jim Giner wrote:
> I"m using basic auth for a few of my pages that I want to limit access to -
> nothing of a sensitive nature, but simply want to limit access to. Want to
> implement a signoff process, but can't figure it out.
>
> From the comments in the manual I t
I"m using basic auth for a few of my pages that I want to limit access
to - nothing of a sensitive nature, but simply want to limit access to.
Want to implement a signoff process, but can't figure it out.
From the comments in the manual I take it one can't do this by simply
unsetting the PHP_
This is a problem I had with my onw control panel for letting logged
in users use phpmyAdmin.
I just setted in the redirection script the $_SERVER['PHP_AUTH_USER']
and $_SERVER['PHP_AUTH_PW'] so the popup dont show up. But if cpanel
dont use PHP, and just passwd file with an .htaccess file, NO WAY
> > My questions:
> > How do I know where to send the data? (eg: which is the authenticating
> > file?)
> > Do I pass it as a GET or a POST or what? URL encode?
>
> You need to tell the browser to use the log in credentials, this is done
> by redirecting the browser to http://username:[EMAIL PROTEC
Ryan A wrote:
Hi,
A client is selling hosting from his site, and _his_ clients get their own
control panel from CPanel,
for the sake of understanding I will name my client A and his client(s) B.
When B needs to log into his cpanel he basicially goes to his a url like
this:
http://hisSite.com/cpanel
6 PM
> To: [EMAIL PROTECTED]
> Subject: [PHP] PHP - Basic Auth - Cpanel
>
>
> Hi,
> A client is selling hosting from his site, and _his_ clients
> get their own control panel from CPanel, for the sake of
> understanding I will name my client A and his client(s) B.
>
>
Hi,
A client is selling hosting from his site, and _his_ clients get their own
control panel from CPanel,
for the sake of understanding I will name my client A and his client(s) B.
When B needs to log into his cpanel he basicially goes to his a url like
this:
http://hisSite.com/cpanel/
then the Ba
[snip]
Please CC me, I am on digest
--
If I have a directory like:
$HOME/www/ (document root)
It has a auth section in the .htaccess file
$HOME/www/.htaccess
another directory like:
$HOME/www/want_to_be_public/
How can I defeat the auth section in the
$
Please CC me, I am on digest
--
If I have a directory like:
$HOME/www/ (document root)
It has a auth section in the .htaccess file
$HOME/www/.htaccess
another directory like:
$HOME/www/want_to_be_public/
How can I defeat the auth section in the
$HOME/www/.ht
Please CC me, I am on digest
--
If I have a directory like:
$HOME/www/ (document root)
It has a auth section in the .htaccess file
$HOME/www/.htaccess
another directory like:
$HOME/www/want_to_be_public/
How can I defeat the auth section in the
$HOME/www/.ht
Please CC me, I am on digest
--
If I have a directory like:
$HOME/www/ (document root)
It has a auth section in the .htaccess file
$HOME/www/.htaccess
another directory like:
$HOME/www/want_to_be_public/
How can I defeat the auth section in the
$HOME/www/.ht
That is one way to try it but I haven't been able to get it to work.
Questions about PHP variable authentication through .htaccess protected
directories has been brought up many times since I've been on this list
but has never been completly answered. Apparently it cannot be done. The
closest thi
I have a issue with basic auth which I hope someone here can throw some
light on.
1) I have already got my SESSION auth working well
2) Once someone logs in I need to send some basic auth info to a dir on
another server to let my logged in user to view it. This is where I am stuck
:-(
I think on
26 matches
Mail list logo
