Maybe I'm too old a dog to teach a new trick to.
I've got the redirect example discussed a couple days ago working
nicely. Back, Refresh, 'wrong username' - all work nicely.
But I like the idea of reducing the load on the server, maybe
alleviating some redirect pinball. So been trying to use
1. p1.php would post to itself. Do data validation. After data validation
upon error, include p1.php again with included error messages
upon success, redirect to p3.php with congrats.
Yeah, I could do this, but it uses a redirect, and like you said, it's gnarly.
2. p1.php
When it comes to liability, who is liable, the merchant running the system,
the develper that created the system, or both?
If the develper is included, would that be mitigated in that he created the
system to the merchant's specifications?
Also, in terms of the developer, would this be
And I basically completely disagree with the author in the first
place, so...
Well, that's been clear for a year. :)
(P.S. I'll get to the issue of rearchitecting this via require instead
of using header() redirects,cough, cough, Richard Lynch, cough, cough
:) in a future message. One
I've been reading up on login mechanisms using redirects, and have a
basic mechanism down.
a1.php:
?php
$site_title='My Site';
if (isset($_SESSION['errmsg_s']))
{$errmsg = 'Warning! '.$_SESSION['errmsg_s'].'!';}
else
{$errmsg = ''; }
if (isset($_SESSION['email_s']))
{
a standard HTTP request is a GET request.
I guess I'm just missing some basic definition of terminology. Been
writing desktop systems for too long, 'spose.
using firefox and one of a number of extensions (firebug springs to mind)
you can actually view the request headers that are sent.
On Saturday 15 December 2007 18:59:12 Richard Lynch wrote:
On Fri, December 14, 2007 11:03 am, Adam Williams wrote:
$query = sprintf(SELECT * FROM users WHERE user='%s' AND
password='%s',
mysql_real_escape_string($user),
mysql_real_escape_string($password));
OK, I've read every message on the list for the last year that contains
'sessions'. I've read through (bleary eyed, admittedly)
http://us2.php.net/session. And I swear, honest, that I had this working on
another box (which is no longer available to me.) I've checked phpinfo -
session support is
Aw crap. :)
(session_save_path BEFORE session_start.)
Works fine now... now to clean the egg off face.
Thx,
On Dec 12, 2007 11:31 PM, Casey [EMAIL PROTECTED] wrote:
Read manual please.
http://us.php.net/session_save_path
--
RE, Chicago
9 matches
Mail list logo
