[any_cfm_file.cfm/my_variable_name=variable_value] -Doesn't seem to work in MX 7

[whyMX]

Hello,

We have recently upgraded to Cold Fusion MX 7, and have problems on many of
our media serving applications that used the format:

[url]http://...../file.cfm/[/url][unique_id]/[format]/[desired_filename].ext

This is because we want to serve the files using cfcontent (they cannot exist
on the hard drive for security reasons), and instead of the users being
prompted to save "file.cfm" we want a more meaningful extension to be displayed
([desired_filename].ext).

This has worked well since CF 4.5 and doesn't work anymore. Have checked
server extensions in IIS 5.0.. here are some results:

Disable script access for .cfm files >> 501 Access denied
Enable "Check file exists" flag >> 404 File not found
Reset default settings [script access on, check for file off] >> No error,
connection closed. Presumably due to an internal error in CF / jRun?

We are using IIS 5.0 on a windows 2000 platform, with Cold Fusion Enterprise
7.0 on a uniprocessor server.

Any help is greatly appreciated. Macromedia: We cannot possibly make your
product a feasible solution in our production environment until this problem is
fixed so please help.

Cheers
Joel

[Abinidi]

Did you uncomment out the lines in the web.xml according to the install docs?

[Tom Jordahl]

If you are trying to use the "path-info" functionality, it should work
assuming you have the correct ".cfm/*" mapping in the web.xml. The
standalone CFMX 7 server should have this turned on by default. Any J2EE
configuration does not.

> Macromedia: We cannot possibly make your
> product a feasible solution in our production environment until this

problem is

> fixed so please help.

Technical support is the right place for critical problems like this. These
forums are NOT official Macromedia technical support, although we try to
help out where we can.

--
Tom Jordahl
Macromedia Server Development

[whyMX]

Hello,

All apologies for my macromedia comment..

Thankyou, that did it. It was the j2EE configuration.. will remember that

Cheers