Usually an authentication handler will send the user_agent a redirect header 
(for security) and start a new session on success, this handler could save 
parts of the POST payload against that session (remember to filter this data) 
so that when the user_agent makes the GET request to the new URL the session_id 
is transmitted and your application can access the session data, any make 
changes to the response: "hi filtered(_user_), haven't seen you since 
filtered(_db_lookup_)". 
In other words your handler should lookup the supplied POST credentials in db 
saving the data retrieved from the db (perhaps last login, email address ...) 
to a new session, and only then send the redirect (302) 

Sent from my BlackBerry® wireless device

-----Original Message-----
From: Tracy12 <[EMAIL PROTECTED]>

Date: Tue, 13 May 2008 20:21:01 
To:users@httpd.apache.org
Subject: [EMAIL PROTECTED] Is this a know issue


Hi,

We have Apache Auth handler writting in mod_perl, after success full
authentication (after the execution of auth handler).

The request parameter came as POST data is lost, but if I send the same
parameters with GET those are available.

What is the reason for this, and how to preserve the post data came in and
use in subequent processes after the execution of auth hanlder.

Waiting for a early reploy
Thanks
-- 
View this message in context: 
http://www.nabble.com/Is-this-a-know-issue-tp17222678p17222678.html
Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
   "   from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to