Instead of using this link:
mysite.com/index.cfm?var1=val1&var2=val2&var3=val3
You'll use this:
mysite.com/index.cfm/var1/val1/var2/val2/var3/val3
First, make sure you can do it the way I'm going to show you. A little test on your web site. If you fail this test then move on to something else because I can't help you, maybe.
Test:
Go to your site and put /var1/val1/var2/val2 at the end of a page url an try it out. What do you see? If the page shows a big fat error message, then you have a problem and I can't help you, bye bye. Oh wait.. Do you have access to the web.xml file of the server? That's in the WEB-INF directory. If your on a shared hosting, then probably not. But if so, add this or find it in that file and uncomment it (unsupported in Tomcat and SunONE servers):
Moving on..
Once you get that part varified or working there's three simple things you must do to use SES urls.
First you must use SES url links. This means that when you create an "a href" link, to use /*/*/ instead of ?*=*&*=*. Get my drift? Duh.
Second, you must parse all that stuff back into url qury_string so your page can use them as normal. Even though you use /color/red/shape/square, your site needs to see and use url.color=red and url.shape=square. Here's the code and I would suggest you use it in your Application.cfc's request function:
And most importantly, unless you can find a better way to beat this, you now have to use fully qualified urls almost everywhere, this means to use your full domain path instead of relative links. Not in things like img tags or cfincludes, but mostly all href links. I have a pretty elegant way of using the application scope to paramaterize it site wide. Existing sites may need to do some find and replacing at href's.