« Previous Next »

• 05-28-2007, 6:26 PM

  armanddp Joined on 05-01-2007, 1:18 PM Posts 2

  Directory Listing Denied Reply Contact I know this is probably not directly related to the FastCGI handler but after configuring my site in IIS to support Ruby on Rails following the 10 steps instructions over here I can't get the default document to work. i.e., when people browse to http://mysite.com/ they get directory listing denied but when browsing to a controller fastcgi kicks in and my Rail application works. I know I'm missing something obvious but for the life of me can't get it to serve a default document. I've tried various default document combinations. Tried the isapirewrite4 filter to rewrite requests to dispatch.fcgi and in a short ritual offered a small chicken to the web gods but still no luck. Any suggestions would really be appreciated. (Great work on the fastcgi handler, apart from the default doc issue it seems to be working like a charm)

  Tags: FastCGIRubyOnRailsrails

• 05-31-2007, 11:33 AM

  In reply to

  jeff@zina.com Joined on 09-26-2003, 10:43 AM Naples, FL, USA Posts 2,096

  Re: Directory Listing Denied Reply Contact The basics of a default document are having the document name in the default documents list on the document tab, preferably only the one or at least with that as the first, and in the directory you're accessing.  The only other restrictions would be no handler for the default document, a file permission denying read access on that file or an ISAPI filter or other security mechanism that blocks serving that extension.  For example, if you run URLSCan or the Lockdown Tool you may lock out your default document from being served.  Check the URLScan.ini and log file for that one. Jeff Look for Wrox's new book Professional IIS 7 in your local bookstore, or order now at Amazon.com

• 05-31-2007, 11:51 AM

  In reply to

  armanddp Joined on 05-01-2007, 1:18 PM Posts 2

  Re: Directory Listing Denied Reply Contact Thanks for the reply. It's a little more complicated than that since there would be no physical files. The content is generated by Rails and the problem in this case I suspect has something to do with the isapi rewrite module I use and the way RoR caches responses. When the cache contains a response for a url that can be mapped back to a url that exists in the default documents list everything works fine. However when just hitting the root before the cached doc is generated for some reason the request is never resolved and the cached document never created. It's only created when I hit the url i.e., index.html directly after which new requests to root works. I'm sorry as this probably don't make any sense at the moment, I'm on the road and will post a better explanation of the problem and possibly resolution when I'm back at the office. The problem doesn't seem to be with the FastCGI handler but rather with the ISAPI filter I use to rewrite requests.