Skip to main content
Inspiring
July 19, 2018
Question

IIS/ cfm page / 404 Issue

  • July 19, 2018
  • 2 replies
  • 4102 views

I have a virtual website running off of IIS (looks like version 8.5,) and ColdFusion 11.

When I access a page as http://something.example.org/ which uses a ColdFusion template (index.cfm), the page correctly displays. However, when I request http://something.example.org/index.cfm it results in a 404.

All .cfm pages result in a 404

Other virtual websites on the same server behave correctly, returning successfully for both http://other.example.org and http://other.example.org/index.cfm

Since I just set up this new website, I'm wondering if there is an additional setting I'm just missing that prevents this error from occurring?

Pages with non .cfm extensions, like .htm & .pdf display properly.

This topic has been closed for replies.

2 replies

weezerboyAuthor
Inspiring
July 22, 2018

Thank you to everyone who responded to this question.

This is a real all-star team of CF gurus.

Every answer was the correct answer.

Thank you, everyone!

Adobe Expert
July 19, 2018

There is a conflict between your ISAPI Filter settings, your handler mappings, and your jakarta virtual directory. Usually, this can best be addressed by uninstalling and reinstalling the connector.

Dave Watts, Fig Leaf Software

Dave Watts, Eidolon LLC
weezerboyAuthor
Inspiring
July 19, 2018

Dave,

I see the Jakarta directory under the Default Web Site directory. Is this the jakarta virtual directory? Is this the only Jakarta virtual directory?

  1. How do I uninstall it?
  2. How do I reinstall the connector?
  3. Is jakarta the connector?
Priyank Shrivastava.
Community Manager
Community Manager
July 20, 2018

Sorry. So I don't currently have a Jakarta directory in my site. So I should just install it, as there is nothing to uninstall. correct?


Hi,

If you have followed the lockdown in your server, please check for the /jakarta directory, if it is set to DENY. If, yes then it will not work, you have to allow it.

To check this in IIS, open the IIS>Request Filtering>URL.

Also, please check Dave's suggestion.

Thanks,

Priyank

Thanks,Priyank Shrivastava