Hi Brad,
Apologies for the delayed response. I was out of town for the last 4 days.
Basically, the URI needs to contain some kind of 'key' that Tomcat can use to know how to pass the request off to the correct servlet. Some successful SES implementations I've seen rewrite all requests to a single index.cfm file, which then routes the response to that request using code - FW/1, Mura, and Taffy all use this kind of SES mapping.
So a URI of '/someDirectory1/main' would be rewritten to '/index.cfm/someDirectory1/main/' in the web server, which Apache and Tomcat know how to route because it contains the 'key' of index.cfm. The translation of /someDirectory1/main is then handled within the CFML code.
Alternatively, other J2EE servlet engines, like Jetty, *DO* support multiple wildcard mappings (like '/*/index.cfm/*'), but they're less known and it's harder to find support for them then it is for Tomcat, so it depends on how important those various aspects are to you.
Hope this helps.
Sent: Wednesday, August 19, 2015 6:31:16 PM
Subject: Re: [Lucee] SES URLs below web root...
Jordan, thanks for the reply, I'm having a hard time figuring out a method
that will work for me. I'd like one rule or method that will allow any
subdirectory to use the SES method, as in /someDirectory/index.cfm/main
without having to create a new rule for each one...
I'm using Apache forwarding to Tomcat. I know that the URLs are getting
passed to Tomcat fine, because Tomcat is returning a 404. Is it possible
using UrlRewriteFilter (
tuckey.org) to create a single rule that would
work in this situation or is it still a case of needing to add each path as
a rule...
> email to
lucee+un...@googlegroups.com <javascript:>.
> To post to this group, send email to
lu...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/291600a6-f75c-4412-b3c1-a88ea91fcfc7%40googlegroups.com.