Question

Just fired up a fresh Windows Server 2008 instance on Amazon EC2 to begin messing around with the ColdFusion 10 beta and ran into an interesting issue.

This WORKS and properly renders the default index.cfm in the root: mydomain.com/

This however DOES NOT work: mydomain.com/index.cfm

Any .cfm file referenced directly within the url doesn't load but if referenced as the default document in a given directory does work.

Like I said, this is a fresh install with nothing outside of the ColdFusion 10 public beta installed along side IIS 7. Ideas?

Était-ce utile?

La solution

This is a connector issue from within IIS. The IIS CFM Handler Mappings should have been taken care of during the installation process but apparently that didn't happen in this case. It's possible IIS is missing a feature (like ISAPI support) that the connector needs in order to function.

You can try re-installing (and thus re-running the connection process) or you may be able to use wsconfig directly to re-install just the connector bit:

ColdFusion10\config\wsconfig

... whatever is easiest for you.

Autres conseils

Jordan is correct, this is a connector issue with CF10/IIS.

This question is similar to:

Coldfusion 10 on Windows 2k8 - .com/ loads OK but .com/index.cfm gives a 404

I posted an answer to that question that may be useful to others who find this question.

I had the same problem but the "Web Server Configuration Tool" (i.e. wsconfig) did not work for me. My answer to this other question provides info on how to manually install the connector in IIS 7.x.

Licencié sous: CC-BY-SA avec attribution
Non affilié à StackOverflow
scroll top