BlueDragon Blog
Here you'll find tips and information about making the most of BlueDragon, which offers several compelling implementation alternatives for your CFML applications. This blog was created originally by Charlie Arehart, who was New Atlanta CTO from 2003-2006.,He has since moved on to become an independent consultant but continues to answer comments raised in existing blog entries. BlueDragon continues, and you should look to the newer BlueDragon blog, from New Atlanta president, Vince Bonfanti, for more updated information.

Another instance of CFMX 7 "catching up" with BlueDragon? CGI.path_info

« H E For All CFers--not just BD :: BlueDragon Evangelism :: Charlie Arehart :: email
posted Wednesday, 9 November 2005

Looks like CFMX 7 has changed in a way that some may be surprised to hear. Though there wasn't much press about it, the CGI.path_info variable now operates in the logical way that BlueDragon has always worked.

In CFMX 6.1 and before (including CF5 and before), if you requested a template with a URL such as:

http://localhost/somedir/somepage.cfm/test

the value of cgi.path_info would be: somedir/somepage.cfm/test

In CFMX 7 (and as has always been in the case in BlueDragon), it now reports:

/test

What's the difference, and why is it significant? See the discussion in the BlueDragon CFML Compatibility Guide for an explanation.

We also point out there that for those really wanting the path and name of the file, use the cgi.script_name instead (which works the same on CF and BD.)

My title for this entry is a bit tongue in cheek, but it makes a point. Just as with sourceless deployment, deployment on OSX, and more, those who would claim that BD is always playing "catch up" should realize that there are things added in CFMX 7 which BD has long had. Yes, yes, there remain things added in CFMX 7 that we will address in our next release. Each pushes the other. In the end, everyone wins.


comments (2)


1. Jason Egan left...
Wednesday, 9 November 2005 8:12 am

Thank you Charlie! This feeling of "BD is always one step behind" is one of the biggest road blocks we've found in helping people 'open their minds'. The other being that CFML and ColdFusion (as in CFMX 7) are not the same, there is another option.

Looking forward to all of the new features added to the next version of BD that CFMX 7 won't have :)


2. M left...
Wednesday, 9 November 2005 4:28 pm

Luckily Macromedia has fixed their bug in CFMX7, which was already there in CFMX6 and 6.1, regarding programmatically removing tasks with cfschedule so that they are actually removed instead of floating around in server memory acting like ghosts. ... erm .. not?

It has been reported only a dozen times, and still after all those months there is no fix for this very serious issue.