Re: Witango-Talk: Witango and HTTPS

[Robert Garcia]

I do this with several applications, it treats them both as same domain. Also, I have found the best way to detect from your code, whether you are secure or not, is through: <@httpattributes name="SERVER_PORT"> If it returns 443, you are secure. Unless you use non-standard ports. --  Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 13653 West Park Dr Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [EMAIL PROTECTED] - [EMAIL PROTECTED] http://bighead.net/ - http://eventpix.com/ On Mar 7, 2006, at 11:15 AM, Alan Wolfe wrote: Hey everyone,   We are about to start trying to integrate HTTPS into our log in system and i was wondering if there are any issues that arrise from trying to work with HTTPS and witango at the same time?   For instance if im at https://mydomain.com will i have the same domain scope as http://mydomain.com ?   Anything funky like that we need to be aware of?   We were thinking it would be best to have an HTTPS login and then make it go back to regular HTTP after.   TIA for any help! Alan Wolfe ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf