|
|
Posted by klenwell on 10/04/07 16:58
On Oct 4, 5:07 am, Jerry Stuckle <jstuck...@attglobal.net> wrote:
> C. (http://symcbean.blogspot.com/) wrote:
> > On 2 Oct, 17:01, klenwell <klenw...@gmail.com> wrote:
> >> On Oct 2, 5:53 am, "C. (http://symcbean.blogspot.com/)"
> > <snip>
> >>> C.
> >> C.,
>
> >> Do you mind outlining the iframe method you use?
>
> >> Thanks,
> >> Tom
>
> > Page has form with input fields for username and password, a button
> > and and a hidden iframe (uninitialized).
> > User fills in username and password, clicks a button. Button calls
> > javascript to set the location of the iframe passing username as a GET
> > parameter. This location is a PHP script which generates a javascript
> > which is sent to back to the browser, with $s_u and $s_s. Javascript
> > retieves current password value from outer window and hashes it, then
> > puts the value back into the password field and submits the form.
>
> > C.
>
> How much more complicated do you want this? Never mind that it won't
> work for those with javascript disabled.
>
> --
> ==================
> Remove the "x" from my email address
> Jerry Stuckle
> JDS Computer Training Corp.
> jstuck...@attglobal.net
> ==================
Ha. I don't know. Doesn't sound absurdly complicated. I think it's
pretty ingenious myself. And we're in the age of mechanical
reproduction, so if you can proof it out once, after that it shouldn't
be much more complicated than using a regular form.
Javascript point is true, but you can inform those that don't have it
enabled of your intentions.
Thanks, C.
Navigation:
[Reply to this message]
|