>Matt has it right. I'm trying to go for a more professional looking
>thing... and I do want it to display a notice when the login fails. I
>have thought of another way to do it... but it's not pretty, so I'm
>still open to suggestions. A while back I posted a pseudo-code
>explanation of what i
Ahh, and a bit of clarification before you read the code, the page posts
to itself =>
Ben
-Original Message-
From: Dave [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 30, 2001 8:05 AM
To: [EMAIL PROTECTED]
Subject: RE: [PHP] Re: HTTP header question.
below
>Some of the or
gt;
Thanks a pile,
Ben
-Original Message-
From: Dave [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 30, 2001 8:05 AM
To: [EMAIL PROTECTED]
Subject: RE: [PHP] Re: HTTP header question.
below
>Some of the original message:
>> still don't see the need to pass as a header...
>&
below
>Some of the original message:
>> still don't see the need to pass as a header...
>>
>> you avoid the http://his.website.com/rams/login.php?failure=true as you
>just get
>> login.php each time as far as the displayed URL.
>>
>> my opinion, let the scripting handle all the logic and ease off
Some of the original message:
> still don't see the need to pass as a header...
>
> you avoid the http://his.website.com/rams/login.php?failure=true as you
just get
> login.php each time as far as the displayed URL.
>
> my opinion, let the scripting handle all the logic and ease off the header
> f
still don't see the need to pass as a header...
';
#will display login so user doesnt' have to retype
}
?>
you avoid the http://his.website.com/rams/login.php?failure=true as you just get
login.php each time as far as the displayed URL.
my opinion, let the scrip
The easiest solution is to create the failure variable as a session
variable.
-Stewart
-Original Message-
From: Matt Rogers [mailto:[EMAIL PROTECTED]]
Sent: 30 July 2001 04:00
To: [EMAIL PROTECTED]
Subject: [PHP] Re: HTTP header question.
I don't know how to solve your problem, but I d
On Monday 30 July 2001 03:10, Ben Bleything wrote:
> I understand that the POST operation stores the data from the form in
> the message headers... I just need to know which headers, so I can use
> that information to write my own... I basically want to make it seem as
> if the $failure var was P
back to the page.
I'm having NO luck whatsoever with the HTTP RFC's... too thick =>
Thanks,
Ben
-Original Message-
From: Philip Murray [mailto:[EMAIL PROTECTED]]
Sent: Sunday, July 29, 2001 6:06 PM
To: Ben Bleything
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP] Re: HTTP header
> What I'm looking for is a way to do this such that the user does not see
> anything more than http://host.name.here/rams/login.php in their address
> bar when it failed...
Doesn't using a form with its method set to post send the variables through
headers? If that's the case, couldn't you manua
Quoting Ben Bleything <[EMAIL PROTECTED]>:
> I'm fully aware of that. The issue is not the refreshing (that works
> fine)...
>
> Here's a little more detail:
>
> if(!$login)
> {
> if($failure)
> // complain
>
> // show the form
> }
> else
> {
> if(user_is_good)
I'm fully aware of that. The issue is not the refreshing (that works
fine)...
Here's a little more detail:
if(!$login)
{
if($failure)
// complain
// show the form
}
else
{
if(user_is_good)
// take them to the next page
else
12 matches
Mail list logo
