I wouldn't trust the InetAddress. Its a "best-effort" which may or may not return what you're looking for. I'm also not sure how it functions behind things like content switches, etc.
-Scott On Dec 21, 2007 2:54 PM, Andrew R Feller <[EMAIL PROTECTED]> wrote: > Anyone? > > > > Andrew R Feller, Analyst > > University Information Systems > > 200 Fred Frey Building > > Louisiana State University > > Baton Rouge, LA, 70803 > > (225) 578-3737 (office) > ------------------------------ > > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On > Behalf Of *Andrew R Feller > *Sent:* Thursday, December 20, 2007 8:05 AM > *To:* Yale CAS mailing list > *Cc:* Brad A Cupit > *Subject:* CAS Client cas.client.server property > > > > I know this subject has been beaten into a bloody pulp earlier ( > http://www.nabble.com/forum/ViewPost.jtp?post=12430002&framed=y), however > my colleague has brought up a couple of good questions: > > > > 1. Why can't the client machine determine its name from InetAddress > instead of host headers? Does InetAddress depend upon host headers or DNS > lookups? > 2. Are there any security implications on using the InetAddress? > > > > Thanks, > > > > Andrew R Feller, Analyst > > University Information Systems > > 200 Fred Frey Building > > Louisiana State University > > Baton Rouge, LA, 70803 > > (225) 578-3737 (office) > > > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > > -- -Scott Battaglia LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
