I've always had an idea of randomizing a form element's name and passing
that random name to the following page to force the browser to not
autocomplete the information (it can't pre-populate if it's never seen the
form name before).

I've never actually worked out how to do this mainly because I've never had
to but I don't think it's very hard. Perhaps randomize the username field
and then have a hidden field named "username" and have the value as the
"real" username element's random name so you have access to it.

Just an idea.


On Wed, Nov 4, 2009 at 12:55 PM, Ian Skinner <h...@ilsweb.com> wrote:

>
> DURETTE, STEVEN J (ATTASIAIT) wrote:
> > One reason could be Corporate policy.
> >
> > I know one company for sure that will not be named that has a policy
> > that states that user id and password fields will be blank.
> >
> > Even though they lock down the browser not to auto populate, some people
> > could still get past it.  Then for some reason, the powers that be
> > always go for the programmers.
> >
> > Just one possibility.
> >
> > Steve
>
> And I presumed that this, or something very similar, was the driving
> force behind the original question.  And, unfortunately, the main
> problem with your scenario is the powers that be going for the
> programmers - who only have an illusion of control, rather then the
> employees who are breaking the policy.
>
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Want to reach the ColdFusion community with something they want? Let them know 
on the House of Fusion mailing lists
Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:328016
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Reply via email to