That's just as easy to spoof as http_referer.  Better to do what Jerry
suggested and use a UUID in a hidden field that is also stored in the
session/client scope for validation on submit.

Cheers,
barneyb

> -----Original Message-----
> From: Mike Kear [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 10, 2004 7:26 PM
> To: CF-Talk
> Subject: RE: http_referer
>
> You can't rely on cgi.http_referer.  Not all browsers pass
> it.   Either
> because the software just doesn't, or because the users disable it for
> privacy reasons.  
>
>  
>
> If you really need to pass that across, then I'd suggest
> creating a hidden
> field on the previous page containing cgi.Script_Name that gets passed
> across.  That way you're controlling it yourself, and can
> guarantee the
> information.
>
>  
>
> Cheers
>
> Mike Kear
>
> Windsor, NSW, Australia
>
> AFP Webworks
>
> http://afpwebworks.com
>
>  
>
>  
>
>   _____  
>
> From: Andrew Grosset [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 11 May 2004 11:23 AM
> To: CF-Talk
> Subject: http_referer
>
>  
>
> Is there an alternative to cgi.http_referer when checking that a form
> submission originated from the form page?
>
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to