fburleigh
Wed Oct 25 12:43:57 CDT 2006
Oh man...I'd looked at that ten times last night but was really looking
at the document options! Anyway, it's better now. Thank you so much!
Kristofer Gafvert wrote:
> Hello,
>
> 403 with substatus code 1 means "Execute access is denied". Can you please
> verify that execute permissions is set to atleast "Scripts" (and not None).
>
> To do this:
>
> Right click the website and click Properties.
> Click on the Home Directory tab.
> Change Execute Permissions
>
> Hope this helps.
>
>
> --
> Regards,
> Kristofer Gafvert
>
http://www.gafvert.info/iis/ - IIS Related Info
>
>
> fburleigh@gmail.com wrote:
>
> >- a failure:
> >2006-10-25 04:57:39 129.79.131.64 GET /index.shtml - 80 - 156.56.75.77
> >Mozilla/5.0+(Windows;+U;+Windows+NT+5.1;+en-US;+rv:1.8.1)+Gecko/20061024+BonEcho/2.0
> >- ccdps.indiana.edu 403 1 1918 403
> >
> >- a success:
> >2006-10-25 04:57:51 129.79.131.64 GET /index.html - 80 - 156.56.75.77
> >Mozilla/5.0+(Windows;+U;+Windows+NT+5.1;+en-US;+rv:1.8.1)+Gecko/20061024+BonEcho/2.0
> >- ccdps.indiana.edu 200 0 427 502
> >
> >Thanks Ken.
> >
> >Ken Schaefer wrote:
> >>Please post the relevant IIS log file entries.
> >>
> >>Thanks
> >>
> >>Cheers
> >>Ken
> >>
> >><fburleigh@gmail.com> wrote in message
> >>news:1161752163.840580.218730@k70g2000cwa.googlegroups.com...
> >>>Right, it's server side includes failing on IIS 6 on patched Server
> >>>2003. I've created a new "site" that is associated with a host header
> >>>(the machine has multiple "sites"). This new site answers to
> >>>index.html but not index.shtml. The index.shtml file does not actually
> >>>include any other files. Permissions on both files appear the same. I
> >>>see the 403 errors both at the browser and in the site's logs.
> >>>
> >>>What I've done:
> >>>
> >>>- "Server Site Include" is allowed in the web services extensions
> >>>console
> >>>
> >>>- Under "application extensions" mappings for the site, I see shtml
> >>>associated with ssinc.dll for the GET and POST verbs
> >>>
> >>>I shut down and restarted the site, thinking it might not have picked
> >>>up these changes. I've also restarted the default application pool.
> >>>
> >>>My guess is that this new "site" hasn't found that SSIs are allowed.
> >>>In every way that I can see through the UI, this site is the same as
> >>>two others where I don't see this problem.
> >>>
> >>>Suggestions would be much appreciated.
> >>>