开发者

HTTP Error 403 - Forbidden

开发者 https://www.devze.com 2023-02-16 03:01 出处:网络
When I start Debugging on asp.net3.5 . Browser display bellow message *Server Error in \'/attn-web\' Application.

When I start Debugging on asp.net3.5 . Browser display bellow message

*Server Error in '/attn-web' Application.

HTTP Error 403 - Forbidden.

Version Information: ASP.NET Develo开发者_运维知识库pment Server 9.0.0.0*


It might be an issue with NTLM Authentication.

  1. Right-click on your solution in the Solution Explorer.
  2. Select Property Pages.
  3. Select Start Options in the dialog.
  4. In the Server section, uncheck NTLM Authentication


If you have Vista or Windows 7 try running the Visual Studio as administrator (right click the EXE and choose "Run as administrator") as it might be some security/permissions issue.


I was getting following issues, after trying their solutions i got this same error message

WCFTestClient The HTTP request is unauthorized with client authentication scheme 'Anonymous' (my service is a non-WCF service)

The HTTP request is unauthorized with client authentication scheme 'Ntlm'

and finally got the solution from here which is In the Server section, uncheck NTLM Authentication (Project Properties -> Web -> Servers)


  1. Firewall,
  2. bad 'hosts' file,
  3. aspnet server configuration problem,
  4. Folder security restrictions

..

Try to look at log files (Win+F, select folder /Windows and specify to find fresh files) and 'Event Viewer' (Press Win, then type: Event Viewer)

P.S.: Nothing personal, but your question is really unclear.


you just need to change the specific port you are using:

  1. Right-click on your project in the Solution Explorer.
  2. Go to Properties.
  3. Select Web in the dialog.
  4. Change the Specific port to anything else e.g. 44444

hope this is the solution for your problem


It happened to me too. I had moved the project and fetched it again. It turns out that Visual Studio binds the virtual directory name as the source path for the files, and moving a (physical) directory makes IIS adjust the virtual directory to the new path. Visual Studio uses the virtual directory name still, and that causes a conflict.

Deleting in IIS the virtual directory made things work again.


I also had the same problem. This is how I solved it. I think this may be helpful for you.

1. Go to "start" and then type IIS(Internet Information Services) and hit Enter
2. In the right side there are "connections"
3. Go to "sites"-> "Default Web Site" which is located inside the connections
4. Double click the "Default website"
5. There in the features view double click the "Directory Browsing"
6. In the right side there are the actions if "Enable" is available double click on that (Otherwise that feature is all ready available)
7. Then go back to the previous page
8. Double click on "Default Document"
9. There you can see a list of default documents
10. If your default document for the website is not available you can add it by clicking the "add" in the right side and there type the name of your default document.

0

精彩评论

暂无评论...
验证码 换一张
取 消