error 401 on "path access" restrictions

[muteinvert]

i made path access for some folders on my site(and yes, i did it right), but when i go to them it directly goes to a 401 error without asking to login. i have tried other browsers(opera, netscape, using IE) and all of them do the same thing. is this a bug or something?

[Anonymoose]

AFAIK a 403 Forbidden error should be the result of failed authentication...

What happens if you try to access a folder that has protection in the http://username:password@yourip format ? This won't work in IE after the latest security update, but should still work in Mozilla/Firebird/Opera if you test with them...

[muteinvert]

amazingly, the "http://username:password@yourip" thing seems to work. but my problem is, specifically, that you have no way of authenticating yourself because it doesn't ask you for anything, just directly gives a 401. i've searched the forums, and this happens to other people too, for no good reason is seems.

[Anonymoose]

Any chance of a look through your conf file - delete the passwords from the usernames and paste it to a PM :D Alternatively you can wait for Aprelium - I'm sure they'll also offer to take a look for you :)

[Anonymoose]

1) Could you remove your custom error pages + the configuration for them in the console and test it again ? See if you get a normal 401 or if it works properly...

2nd in PM.

[TRUSTAbyss]

I always know this problem , don't setup a default error page
it ruins the whole process of password protection , add a custom
error page and use each error code as 404 , 403 , 200 ect. 8)

[aprelium]

When configuring the custom 401 error page, you must associate it with a virtual path that looks like /path/to/401/errorpage.html . If you configure it as a full URL http://mysite/path/to/401/errorpage.html, you will have problems with the authentication.
_________________
Support Team
Aprelium - http://www.aprelium.com