I uploaded a new/default version of 1.5.0.1 to an IIS server, and when I try to access the site, (www.mysite.com/cifolder) I get a ci 404 page not found error.
However, when I type in www.mysite.com/cifolder/index.php/welcome it brings up the welcome page (default controller) just fine like normal.

I try this same thing with 1.4.1 and it works fine when I type the base url (www.mysite.com/cifolder), meaning it brings up the default controller.

This apparently doesn’t affect apache, because it works there.

I haven’t found the bug behind this, but thought you should know.

Any help on fixing this would be appreciated. Thanks.

What about the default page for that site - does it have index.php in it? And what happens if you just go to /cifolder/index.php? (Without the controller name)

Hi Craig,

“What about the default page for that site - does it have index.php in it?”

What do you mean exactly? Do you mean default controller? Sorry for not following.

And what happens if you just go to /cifolder/index.php? (Without the controller name)

When I do this, it still says page not found (the ci version, not a regular iis 404 looking error)

Hi. I meant the default index page that can be configured through IIS for a given site/directory - shown in this image.

However, CI should still be loading the default controller when you go to /index.php. Unfortunately I don’t have an IIS + PHP installation to test this on, sorry.

Oh, I see. Yes, I assume in IIS, index.php is configured because CI 1.4 works just fine.
It’s my host. I can’t change anything on the IIS side.
I can’t even enable logging because they don’t allow php to create files, for security reasons.

Guess I’ll go back to 1.4 for this app, and wait for a bug fix.

Long live Apache!

Or ditch the IIS host altogether

I do have access to IIS at work, but it’s on a domain controller/file server etc. so running PHP on IIS would push it over the edge I think I agree, go with Apache