cflogin _can_ use http authentication, but it doesn't have to. 

========================================================================
===
Raymond Camden, ColdFusion Jedi Master for Mindseye, Inc
(www.mindseye.com)
Member of Team Macromedia (http://www.macromedia.com/go/teammacromedia)

Email    : [EMAIL PROTECTED]
Blog     : www.camdenfamily.com/morpheus/blog
Yahoo IM : morpheus

"My ally is the Force, and a powerful ally it is." - Yoda 

> -----Original Message-----
> From: webguy [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, June 10, 2003 9:59 AM
> To: CF-Talk
> Subject: RE: J2EE Sessions in JSP/Servlets , CFM's and CFLOGIN
> 
> 
> AFAIK, cflogin uses http authentication. That would mean that 
> the username is passed in the HTTP request headers.
> 
> <cfdump var="#GetHttpRequestData()#"/> and see what you get
> 
> They should be available to java the same way any request 
> headers are..
> 
> WG
> 
> -----Original Message-----
> From: Reilly, James [mailto:[EMAIL PROTECTED]
> Sent: 10 June 2003 16:44
> To: CF-Talk
> Subject: J2EE Sessions in JSP/Servlets , CFM's and CFLOGIN
> 
> 
> I know that JSPs/Servlets and CFM can share the session 
> scope, but what about the CFLogin scope? (Cflogin scope seems 
> to be like a private scope, since the session scope does not 
> hold the CFLogin related info.)
> 
> So, how can a jsp/servlet "see" the CFLogin data, with out 
> passing it around...?
> 
> Tkx,
> Jim
> 
> 
> 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq

Host with the leader in ColdFusion hosting. 
Voted #1 ColdFusion host by CF Developers. 
Offering shared and dedicated hosting options. 
www.cfxhosting.com/default.cfm?redirect=10481

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to