wood burning stoves 2.0*
The moose likes Servlets and the fly likes POSTing to authenticated URLs Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » Servlets
Bookmark "POSTing to authenticated URLs" Watch "POSTing to authenticated URLs" New topic
Author

POSTing to authenticated URLs

Nathaniel Stoddard
Ranch Hand

Joined: May 29, 2003
Posts: 1258
Is it possible for a POSTed form's data to remain intact across a form-login authentication scheme? The servlet spec says for login-form authentication, it will "save the URL path" that triggers the authentication, and use it after the user successfully is authenticated.

I'm guessing that ambiguity will lead to server mismatches--some being able to reconstruct the full request after authentication, while others only reconstruct the request but miss the message body.

On a related note, after the user gets authenticated, is there any difference between the original request and the one that you see after authentication? Will, for example, the referring URLs be identical, or will the final one be changed to reflect some bizarre authentication URL the container comes up with?


Nathaniel Stodard<br />SCJP, SCJD, SCWCD, SCBCD, SCDJWS, ICAD, ICSD, ICED
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 60782
    
  65

Seems more appropriate for the Servlets forum.
[ October 28, 2004: Message edited by: Bear Bibeault ]

[Asking smart questions] [Bear's FrontMan] [About Bear] [Books by Bear]
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 15958
    
  19

First of all, POST contains 2 types of data to worry about: the URL itself, plus the data stream that was POSTed. That's different from GET, where the URL is all you get (discounting side stuff like cookies).

Your URL may get rewritten when you authenticate to add session ID info, but the core URL should not. If you use the URL data extraction services that should make for minimal effect. If you're doing the parsing yourself, YMMV.


Customer surveys are for companies who didn't pay proper attention to begin with.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: POSTing to authenticated URLs
 
Similar Threads
Form based authentication with Tomcat 7 and JSF2 Problem
Redirect to the requested page failed using form-based authentication
pre or post filter j_security_check
Best practice for secure login authorisation
POSTing to authenticated URLs