Re: BIG WARNING - validation controls appear to be ignored.

From: Andy Fish (ajfish_at_blueyonder.co.uk)
Date: 02/26/05

  • Next message: D: "Using ImpersonateLoggedOnUser" 
    Date: 26 Feb 2005 09:20:32 -0800

    >
    > You miss the point of his comment, which has nothing to do with the
    > docs, and everything to do with not depending on validators to protect
    > your backend data.
    >
    > That's called defense in depth, and is the practice of good
    > programmers.
    >

    Just as a follow-up, the point of my original comment was not really
    about relying on client-side validation. no programmer worth his salt
    would ever do that deliberately.

    My point was that the system as a whole (the framework and development
    environment) did not "fail-safe". Without reading every word of the
    documentation, I wrote and tested an application making what I
    beleived to be a reasonable assumption about how it would work. When I
    deployed it I found out by accident that it was relying on client side
    validation. IMHO this would be worth a big caveat on every page
    relating to the valiation, not just a single note.

    Better still, I would have click-type events only fire if the form is
    valid, unless the developer specifically overrides this behaviour.

  • Next message: D: "Using ImpersonateLoggedOnUser"

    Relevant Pages

    • Re: BIG WARNING - validation controls appear to be ignored.
      ... about relying on client-side validation. ... no programmer worth his salt ...
      (microsoft.public.dotnet.framework.aspnet)
    • Re: Color Code
      ... hade recieved both color codes. ... merits of client-side validation, while I stubbornly refuse to budge from ... debate on the merits of client-side validation once the original issue has ... server-side validation is put in place to verify those two color codes have ...
      (microsoft.public.inetserver.asp.general)
    • Re: Form no longer submits - client validator problem?
      ... The service pack reference makes me think of this: ... > client-side validation for required fields completely, ... > The event handlers are still in the InitializeComponent so my events ...
      (microsoft.public.dotnet.framework.aspnet)
    • Form no longer submits - client validator problem?
      ... I'm going back to a previous asp.net web project after a few months of ... client-side validation for required fields completely, ... I added a break to the form tag line in the debugger. ...
      (microsoft.public.dotnet.framework.aspnet)
    • Re: BIG WARNING - validation controls appear to be ignored.
      ... > nothing happens on the server. ... However, if client-side validation is ... all control events fire on the server even if the ... > that are unwittingly relying on client-side validation. ...
      (microsoft.public.dotnet.framework.aspnet)
    • Quantcast