To reiterate, this is a brand spankin’ new spin-up of a CF11/Windows Server 2008 R2/IIS7.5 VM. Nothing else has been done to configure this puppy other than pure Windows, IIS 7, CF11, CF11 Update 2, ColdBox 4, and a CB4 app from CommandBox. We have done nothing to enable any rewriting. This is about as plain vanilla as you can get, guys.
Brad, below is server.xml on this installation, so that you can see which Connectors are commented out, and which are not. Again, this has not been touched. When I try to hit the CB app on ports 8500 or 8443, I get nothing.
Your HTTP connector is commented out by default. You’d need to uncomment it and restart CF to hit tomcat directly on port 8500. You may also need to uncomment the Context tag as well. I’ve always just used the built-in web server for CF11, so I’m not positive what Tomcat configs need changed from default to enable it if you installed it with the IIS connectors as the default.
For instance, I currently have my local CF11 install pointed at a test site and this is my context tag from server.xml:
And to be clear, I’m not saying your server.xml settings are wrong-- I’m mostly just trying to eliminate IIS from the picture temporarily to narrow down why the cgi info is wrong.
Alrighty, then! I opened up the Connector on 8500, as well as the Context, restarted CF, hit 8500 directly, and it worked beautifully, without index.cfm in the URL. CGI.PATH_INFO is empty. So what the heck is IIS doing, anyway?!?
We’re going to try making Tomcat default, with an uninstall of IIS.
That’s good-- I think it helps us narrow down the issue to IIS or the IIS connector. Perhaps someone else here can confirm if IIS works for them with CF11. Since I don’t have access to IIS I can’t test it.
My gut feeling is that something is still wrong with your IIS/CF connector, but I suppose there’s always the possibility of a bug in CF11. You could open a ticket with Adobe or E-mail cfinstal@adobe.com to get support for your installation issues. I believe Anit checks the adobe address so you’ll probably get a reply back from him pretty quick.
It works for me with CF11, that’s how I knew there should be no index.cfm in the path_info. But I also have Helicon rewrite installed as well.
I do recall a Virtual Directory mentioned, so there would be two more tests to do.
Compare that the jakarta info is applied to the Virtual Directoy as well as the website root.
Try installing it on a new website in IIS in the root and not a VD and see if it works there.
Other than those suggestions, I am at a loss to explain it further. Also I am not sure if you know this or not, when installing the connectors via the GUI, you WILL need to run that as an Administrator as it will fail and not tell you it failed. Not sure if they have fixed that in any of the patches, as I always run as Admin anyway.