Error: HTTP 405 - Resource not allowed on ASP Page

[nder]

Ok, I have a weird error. I'm working on an intranet site, running on my machine (Windows 2000, IIS 5.0). I have a virtual directory for my application, and IIS is set to load my default page when the URL for the virtual directory is entered. Here is the problem, when the user enters the url to the virtual directory, it loads the default page (Login.asp). However, when they enter their login information and press the submit button, I get a "405 - Resource Not Allowed error".

However, when I hit the Login.asp page directly, everything works fine.

So in summary:

http://mycomputer/myapplication/ - takes me to page, but give 405 error after.

http://mycomputer/myapplication/Login.asp - works fine

Any ideas?

[MadHacker]

Do you have a database linked to the login page if yes
you have to change the security privalage to allow (everyone) to add,write,remove. In the security option of the folder I assume you know how to get there

if that dont work please check the specified line number or send the error message again this time with more detail

[nder]

The pages connects to an SQL Server Database.

I do not believe this is a permission problem. The page works fine if I hit it directly. That is, as long as IIS doesnt forward you to the page as the default page, it works.

[Arch_Angel]

nder, maybe you can post some of your asp code from your login.asp page.

I have some guesses as to why you get the error but I am not 100% on it.

1. Your script is using server variables that is requesting the PATH_INFO or SCRIPT_NAME variables. Doubt it, but worth a check.
2. You haven't specified an ACTION for the form.
3. Your IIS server doesn't have permission to execute the VERB you are using with your form.

As I said, just some things to check. Looking at your code would probably point me to something that might be causing that problem.

[nder]

Thanks AA. It was your second guess. Form was supposed to be self posting, but I hadnt specified the action.

[nder]

I'm curious though, why dont I get the error when I go to the page directly. Gonna research that one.