Mark Lavi <[EMAIL PROTECTED]> wrote:I'm not sure what response you mean, the web browser/client's response to the HTTP headers upon the next HTTP request back to the web server?
This is a follow up on my quest for mod_auth_radius.c Apache module to pass on any additional attributes in an accept-access RADIUS packet. Alan asked that I review my proposal (pass the attributes down to the user's session via the HTTP "Pragma" header field) with Apache folks.
Alan, do you think this is sufficient?
So long as the list of RADIUS attributes don't get sent out in the HTTP response. That's my biggest worry with the use of HTTP headers, and with Apache.
It isn't clear how to keep per-request configuration data, for use by other modules.That would probably extend the scope of this solution a bit further than is necessarily to get things started. I'm not sure another module's utility would be needed, could you elaborate? By passing the attributes, they can be used in the server side environment (CGI/PHP/etc.) and that's the value I am after.
Thanks,
-- --Mark o Atarex Communications: Web, Software, and Network Development /\/ Public key attachment for secure e-mail enclosed. // mailto:[EMAIL PROTECTED] || http://www.atarex.com
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
