That's cool, but a little overkill for some use cases. For instance, in a portlet-based portal application, you might have individual portlets registered to the patterns "/PortletInvoker/MyPortletName". We need the portal to access them, but a user shouldn't be able to access a portlet directly from a URL like "http://myserver/PortletInvoker/MyPortletName";, so I'd like to serve a 404 before that portlet (ie, the servlet that manages it) is hit.
Is there any simple solutions to this problem in Tomcat? Thanks! awarnier wrote: > > > I'm beginning to sound as if I had a sales commission on that module, > but I really like it.. > Also, there might be a better method, but what I'm thinking of would be > based on this module : > > http://www.tuckey.org/urlrewrite/ > > You can test "from where" the request is coming, and in case it is not > "from inside", re-direct it to some standard html page that you would > create on your server, and would look like a 404 response. > I mean that it would not actually be a 404 response (it would be a > normal 200 OK response), but the content of the page would be "sorry, > this URL could not be found". > > > > -- View this message in context: http://www.nabble.com/Is-it-possible-to-%22hide%22-tomcat-resource-from-outside--tp20349038p20599645.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
