Win a copy of Modern JavaScript for the Impatient this week in the Server-Side JavaScript and NodeJS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

need to use ssl on specific folder

 
Ranch Hand
Posts: 127
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i need to use https protocol on specific folder on jsf 1.2 by example or url ,
my users in database and my server shared tomcat

thanks
 
Ranch Hand
Posts: 859
IBM DB2 Chrome Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
folder?

What exactly are you asking?

SSL/HTTPS ?

WP
 
hassan ali
Ranch Hand
Posts: 127
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
asking for https
 
Saloon Keeper
Posts: 22479
151
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
URLs don't have "folders". URLs are not filesystem paths - they just happen to have a similar syntax plus a convention that when the webapp cannot figure out anything else to do with a URL, it disassembles it into a resource path in the WAR. Which may or may not be an actual physical file location, depending on whether the WAR was exploded by the appserver or not.

Having disposed with the pedantry: You can specify a URL pattern that demands secure transport by defining it in web.xml. This DOESN'T protect a "folder", only the URL pattern. If there's some other URL that can also access the resource in question, a separate pattern would have to be defined to restrict it as well.

This protection mechanism is almost identical with JSF as it is with non-JSF with one very critical exception. As you are probably well aware, the URL in the browser toolbar doesn't track the resources being accessed - it tends to lag. Recall, however, that the protection is for the URL, not the "folder", and you can see a problem.

The way to avoid this problem is simple: when navigating to a protected resource in JSF, add the "redirect" element to the navigation rules. That will force the URL to track the resource path by forcing a redirection.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic