it uses https (ssl over http) - deployed app should be accessible on
https://localhost:8181/httpsBasicAuth-webapp/helloworld.
https is the best option for you, but depends on what exactly do you
need - it encrypts all your messages and can take care of authentication
too (when client certificates are used) but you might not need that
level of security. Recommended usecase is basic (or digest) auth over
https, should be sufficient for most cases.
Pavel
On 4/13/11 11:02 AM, steben wrote:
> Hi
> thanks so much for your help,I tried the example and it works well, but I
> have a question is it the best way for securing web service?, because , I
> don't see that it use a protocol ssl wich is a recommended for a web sites
>
> --
> View this message in context: http://jersey.576304.n2.nabble.com/Jersey-https-tomcat-tp6266431p6268229.html
> Sent from the Jersey mailing list archive at Nabble.com.
>