It was a combination of user agent and referer, thanks to all for your
help - I certainly learned something about a tag I had rarely if ever
used before!
On 5/17/05, Jared Rypka-Hauer - CMG, LLC <[EMAIL PROTECTED]> wrote:
> Ahh, thanks Dave.
>
> I was guessing, and I guessed wrong. See what you l
Ahh, thanks Dave.
I was guessing, and I guessed wrong. See what you learn from the lists?
So CFFORM mandates the name attribute to link the validation JS with the
correct form elements... nothing to do with server-side at all. Good to
know.
Laterz,
J
On 5/17/05, Dave Watts <[EMAIL PROTECTED]>
> If you really want to try messing with the form name, you're
> going to have to figure out what sort of header value it is
> and use a different type in a cfhttpparm tag. I don't know
> which one it is, but that'd be about the only way to do it.
The form name is a client-side HTML attribute,
It's possible they're using the image field to verify the validity of the
form post, but unless that IS the case that image field is just a colorful
submit button.
If you really want to try messing with the form name, you're going to have
to figure out what sort of header value it is and use a
Thanks, I'll give it a try.
On 5/17/05, Mosh Teitelbaum <[EMAIL PROTECTED]> wrote:
> Wayne:
>
> I can't say that this is the problem, but your CFHTTP code is not passing
> any values from the Image form field. Image form elements act as pseudo
> Submit buttons except that, instead of just passin
Wayne:
I can't say that this is the problem, but your CFHTTP code is not passing
any values from the Image form field. Image form elements act as pseudo
Submit buttons except that, instead of just passing back a single value (the
value of the Submit button), they pass back the (x,y) coordinates o
6 matches
Mail list logo
