So while ParseURLData will give more control over what happens to the info passed in the "SES" string, using SESconverter will simnply and seamlessly convert it as if a normal URL had been passed - meaning that
index.cfm?foo=bar&this=that is treated exactly the same as
index.cfm/foo/bar/this/that.htm, or even
index.cfm/foo/bar.htm?this=that if you want to mix and match.
Aside from the questions of whether or not search engines prefer SES urls, there is the matter of logs. If you use fusebox (or any method where the index.cfm is the only template called in the browser), the the web logs can be pretty useless - its not earth shattering news that index.cfm is the most popular page.
However, using SES urls can trick the webserver into recording the "page" requested as index.cfm/foo/bar.htm, which could be far more useful. Whether or not the webserver does log the SES portion seems to depend on the version of CF and webserver.
AFAIK, CF5 will never log the SES part with IIS, but CFMX will. I'm not sure about other web servers...
Cheers
Bert
>
> -----Original Message-----
> From: Stan Winchester [mailto:[EMAIL PROTECTED]
> Sent: 03 March 2004 15:59
> To: CF-Talk
> Subject: Re: SES & CFLIB UDF ParseURLData
>
>
> Does anyone have any thoughts on my first questions, which
> is: Has anyone had any experience good or bad with the UDF
> �ParseURLData� found at: http://www.cflib.org/udf.cfm?ID=378
> ? I have tested it locally on my XP Pro/CFMX dev box and it
> seems to work nicely. Peter suggested the �sesConverter�
> found at http://www.fusium.com/ which is another possible
> solution. It is always nice to know the experiences of others
> using a solution like CFLIB �ParseURLData� or Fusium
> �sesConverter�. I like the UDF �ParseURLData�, am open to
> knowing what has worked best for other developers.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
