Ashley M. Kirchner wrote:
> This is probably something that comes up every so often and it's
> generally related to PHP scripts, however I have a different setup and
> am now trying to figure out what to do. On our company site, we have a
> section that clients use to upload files to us throug
You can try an open/close window function, or my personal favorite is just a
couple of pages that use the meta-refresh to jump people to a new page and dump
them through a couple which they would never see, normally 2 is enough to stop
someone from doing it (as well as a logout and making them l
[snip]
I know I can't disable the back button, or clean out someone's
browser history, so I'm looking for other ways, server-side perhaps,
that I can implement to prevent someone from reloading the upload.php
page and try to upload another file (which will generate an error
because the Java
Ashley M. Kirchner wrote:
I know I can't disable the back button, or clean out someone's
browser history, so I'm looking for other ways, server-side perhaps,
that I can implement to prevent someone from reloading the upload.php
page and try to upload another file (which will generate an erro
[snip]
> Can I rely on referrers on upload.php to see where a hit
> came from?
> Or should I redirect to an interim page that simply redirects
> again to the thankyou.php one (which won't stop someone from
> hitting back twice, but it's just an extra thing.) What
> (other) ways have peop
This is probably something that comes up every so often and it's
generally related to PHP scripts, however I have a different setup and
am now trying to figure out what to do. On our company site, we have a
section that clients use to upload files to us through a Java applet.
The way I hav
6 matches
Mail list logo
