Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: Preventing direct URL access in a J2EE environment |
|---|---|
| Date: | Fri, 4 Mar 2005 10:58:42 +1300 |
On Wed, Mar 02, 2005 at 07:54:48AM -0500, Kevin Conaway wrote:
I just want to enforce that users actually click on a link to go to a certain page, not type in the URL manually.
As noted, attaching single-use tokens to each request is the most reliable way of achieving this. A lower-overhead approach (but spoofable, with effort) may be to deny all GETs to the server (other than to the initial "home" page) and have every link submit a POST request. Roy.
| Previous by Date: | Re: Web Scanners, blad3 |
|---|---|
| Next by Date: | Re: Preventing direct URL access in a J2EE environment, Jeroen van Rijn |
| Previous by Thread: | Re: Preventing direct URL access in a J2EE environment, Jeroen van Rijn |
| Next by Thread: | Re: Preventing direct URL access in a J2EE environment, Paul Johnston |
| Indexes: | [Date] [Thread] [Top] [All Lists] |