Hello,
have you tried changing transport-guarantee to CONFIDENTIAL?
Pavel
On 4/12/11 9:32 PM, steben wrote:
> Hi I'm working into securing REST Jersey with ssl using tomcat as a
> server application, I made all changes into the files configuration ,
> but I have always a problem, I can't access to the ressources of the
> web service in browser, while when I try just with http it works well
> Here my web.xml file Jersey REST Service
> com.sun.jersey.spi.container.servlet.ServletContainer
> com.sun.jersey.config.property.resourceConfigClass
> com.sun.jersey.api.core.PackagesResourceConfig
> com.sun.jersey.config.property.packages com.webservive.myservices
> Security for Your Enterprise Your Enterprise web Security Redirect all
> to SSL /* GET POST HEAD PUT OPTIONS TRACE DELETE role1 Protection
> should be CONFIDENTIAL INTEGRAL BASIC role1 also the server.xml of
> tomcat thanks in advance
> ------------------------------------------------------------------------
> View this message in context: Jersey https tomcat
> <http://jersey.576304.n2.nabble.com/Jersey-https-tomcat-tp6266431p6266431.html>
> Sent from the Jersey mailing list archive
> <http://jersey.576304.n2.nabble.com/> at Nabble.com.