PRB: Unable to Access Web Project - Access Forbidden Error

Last reviewed: December 11, 1997
Article ID: Q175800
The information in this article applies to:
  • Microsoft Visual InterDev, version 1.0

SYMPTOMS

The following error occurs when trying to preview a Web site:

   HTTP/1.0 403 Access Forbidden error.

CAUSE

This error is typically caused by either a misnamed document or permissions settings.

RESOLUTION

Misnamed Document

Make sure that the Default.htm or Default.asp file names are listed in the Default Document edit box located under the Directories tab in the properties sheet for the WWW service of the Internet Information Service Manager. More than one type of default page can be listed by including additional names separated by a comma and space (Default.htm, Default.asp, Test.asp, and so forth).

Incorrect Permissions

Make sure directories containing ASP files have Execute permissions. To check Execute permissions open the Internet Service Manager and double- click the WWW Service. Scroll to the directory in question and click Properties. Under Access select the "Execute" option. Directories containing script files, such as ASP files, need Execute permissions to run, but for security reasons should not have Read permissions (if a directory containing an ASP file has Read permissions but not Execute, when the ASP file is requested by the Web client the ASP script code will be displayed in the browser). Directories containing HTML files should have Read permissions.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

Misnamed Document:

  1. Create or open an existing Web project in Visual InterDev.

  2. Rename the Default.asp or Default.htm to a name not listed as one of the Default Documents in Internet Information Service Manager.

  3. Save the renamed file and preview the project in the browser.

Execute Permissions:

  1. Open Internet Service Manager.

  2. Select the Directories tab.

  3. Scroll a directory containing ASP files and open the Properties dialog box.

  4. Clear Execute permissions for the directory in question.

  5. Attempt to browse the ASP page in the directory without Execute permissions.

NOTE: If the directory contains ASP pages and has only Read permissions, the ASP code will be displayed in the browser.

REFERENCES

For the latest Knowledge Base articles and other support information on Visual InterDev and Active Server Pages, see the following page on the Microsoft Technical Support site:

   http://support.microsoft.com/support/vinterdev/

Keywords          : VIASP VIServer kberrmsg
Technology        : kbInetDev
Version           : WINDOWS:1.0
Platform          : WINDOWS
Issue type        : kbprb


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 11, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.