You can't force the browser, it's the server who should support a secure connection..
"The trouble with doing something right the first time is that nobody appreciates how difficult it was!"
Joined: Mar 22, 2005
On your way in you may have missed that JavaRanch has a policy on display names, and yours does not comply with it; specifically, a first name and a last name are required. Please adjust it accordingly, which you can do right here. Thanks for your prompt attention to this matter.
Joined: Mar 14, 2006
Thanks Ulf, indeed I had missed the naming policy...
Joined: Oct 11, 2004
Originally posted by Mandar: You can't force the browser, it's the server who should support a secure connection..
Does it means, HTTPS request doesn't exist, only HTTPS response exist???
And HTTP request and HTTPS response is called secured connection???
This can be done programmatically from within your code or declaratively from the security-constraint entry in your deployment descriptor.
There is a link to the Servlet Spec in my signature. Download the PDF and perform a search with the following criteria: <transport-guarantee>CONFIDENTIAL</transport-guarantee> to learn more about declarative security in j2ee apps.