Hi Paul, That's a very interesting point. I didn't think about that. But isn't it a bad idea to hard-code your path(s) that require SSL. What happens if a decision is made to change the action servlet's mapping from, say *.do to /servlet/*. You would have to remember to change the path(s) in the filter... Furthermore, what if you change the name of the action that requires SSL? Another problem that I can think of is that all the link on the redirected SSL page will be generated with https.
Have you written such a filter? I'd be curious to see how you implemented it. Thanks. Aladin > IMHO, I do not think SSL switching belongs in the Struts framework. I > think most of the time the > correct place to put switching into SSL is in a servlet filter according > to some predefined path. > So if you forward from Struts to a particular location, a filter can then > redirect it to HTTPS. > > Paul > > > > __________________________________ > Yahoo! Music Unlimited > Access over 1 million songs. Try it free. > http://music.yahoo.com/unlimited/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
