I've read people recommend using http authentication for sending usernames and passwords.
I've never been able to get excited about using it because I've always assumed I would be using a reasonably stiff SSL connection to pass the data, and as such I would just post username/password as form values like the rest of the form. Or in the case of ajax/jason I would just include the user/pass as an argument. It takes extra work to include using http authentication, and that seems unnecessary to me since I'm using SSL. I basically don't see the pointing in forking off the credentials and adding additional lines of coding when I could just send the stuff with the rest of the data I'm already sending anyway. Thoughts? Am I missing something? I read this article by Ben Nadel and I still don't see the point. (He's explaining the concept for someone, not necessarily recommending it) http://www.bennadel.com/blog/1574-Ask-Ben-Manually-Enforcing-Basic-HTTP-Authorization-In-ColdFusion.htm -- -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en --- You received this message because you are subscribed to the Google Groups "Open BlueDragon" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
