Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

Archive /

Our old forums are still available as a read-only archive.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo

Admin interface doesn't work on IIS

Go to End

2 Posts   1634 Views


Community Member, 4 Posts

17 September 2008 at 1:55am

Edited: 17/09/2008 2:03am

I installed Silverstripe on an IIS (not because I want to, but it's a requirement..).

I followed the manuals and the forum thread found on and after some modifications found in the forum thread it works, except the admin interface returns different errors, either "page not found (404)" or "unable to process request", depending on whether i log in first using /Security/login.

The regular website is visible, with all links and images etc. working.

This is my current .htaccess:
<open bracket> = [, <close bracket>= ]

RewriteEngine On
RewriteCond %{REQUEST_URI} !(.gif)|(.jpg)|(.JPG)|(.png)|(.css)|(.js)|(.php)$
RewriteCond %{REQUEST_URI} ^(.*)$
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ /sapphire/main.php?url=$1 <open bracket>I,L,QSA<close bracket>

And ideas? Anyone experienced problems with the admin backend on IIS, too?

I'd really like to get this working..


Community Member, 4 Posts

17 September 2008 at 8:02pm

Edited: 18/09/2008 10:52am

I just realized, that the rewriting as such seems to be correct, but that server side redirects are not being rewritten by isapi/rewrite.

E.g. the server correctly rewrites to

If I open, Silverstripe redirects to But after that, the server doesn't rewrite the URL and returns a 404 error, as there is no directory /Security on the server.

The same thing happens with /home, which redirects to / and returns a 'directory listing denied' as it's not being rewritten. Again, opening directly works.

Is there any way to configure (change) this behaviour in IIS? Is this a misconfiguration of IIS? Anyone seen this before?