Mark Lavi <[EMAIL PROTECTED]> wrote: > > 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. > > > 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?
The response from the web server to the browser CANNOT contain any RADIUS attributes. > 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. Where are the attributes passed to, inside of the server? a) environment variables: no, they stick around from request to request b) HTTP headers: no, they get sent back to the browser c) ? Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
