Re: Form validation: client- or server-side?
| From: | Peter Vertes | Date: | Fri, 09 Jan 2004 18:30:32 +0000 |
| Subject: | Re: Form validation: client- or server-side? | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-174160@lists.php.net to get a copy of this message | ||
On Fri, 2004-01-09 at 13:07, Matt Grimm wrote:
> Is there a distinct advantage to doing form validation / error checking on
> the server side using PHP? That's how I've always done it because I know
> PHP better than JavaScript, but wouldn't it make sense to validate as much
> of your form as possible using JavaScript before the form was ever posted?
> I'm just talking about the basics, like empty required fields, illegal
> characters, string lengths, etc.
I would shove off as much work as possible for the client to do on
his/her machine and not bog down my server which could be busy serving
pages/processing bigger and better things. Plus it also cuts down on
bandwidth because you only send the form to the server if the JavaScript
checked everything and didn't find any errors. The downside is that you
have to make sure the client has JavaScript turned on otherwise your
form authentication will not work and the code for your JavaScript is
available to the user to see and if you have any bugs in it then they
can see and work around it.
I guess it would depend on the site you are planning to do the
authentication on. If the site is not super busy, bandwidth is not an
issue and your server is not pegged at 100% most of the time then I
would suggest using PHP to validate your forms because it's "safer"
since the client can not see your code and it doesn't matter if the user
has JavaScript turned on of off. Just my $0.02...
-Pete
--
perl -e 'print pack("H*", "70766572746573406E79632E72722E636F6D0A")'
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc