From: Lenain <le...@gm...> - 2008-10-26 23:24:14
|
Hi, I have difficulties to success WWW-Auth with a .yaws_auth file : I have this virtual host configuration : <server localhost> port = 80 listen = 0.0.0.0 docroot = /home/lenain/www/ dir_listings = true <auth> realm = blah dir = /test/ </auth> </server> And a .yaws_auth file in /home/lenain/www/test/ with only : {lenain,mypass}. Once i reach http://localhost/test/ i'm asked for login/password. But with the previous IDs, i'm asked again for it. :( Did i missed something? Anyway, it works with : <auth> realm = blah dir = /test/ user = lenain:mypass </auth> But it is deprecated isn't it? Excuse my poor English, and thanks in advance for your answers! :) |
From: Claes W. <kl...@ta...> - 2008-10-27 09:21:01
|
Lenain wrote: > > And a .yaws_auth file in /home/lenain/www/test/ with only : > > {lenain,mypass}. > It says in the man page Each row of the file must contain terms on the form {User, Password}. Where both User and Password should be strings. The .yaws_auth file mechanism is not (yet) recursive. Thus any subdirectories to Dir are not automatically also protected. string, the user and password must be strings. As for the deprecatedness, I honestly don't remember why this was deprecated. Seems to naive me, that having the user/pass data in the different directories is possibly better than having it yaws.conf It really ought to be recursive as well. /klacke |
From: Lenain <le...@gm...> - 2008-10-27 13:49:54
|
*cough* Seems that i was pretty tired yesterday evening... always tried with {'lenain','mypass'} rather than {"lenain","mypass"}... Pssh sorry :/ It works fine now :) Thanks again :) Claes Wikström a écrit : > Lenain wrote: > >> >> And a .yaws_auth file in /home/lenain/www/test/ with only : >> >> {lenain,mypass}. >> > > It says in the man page > > Each row of the file must contain terms on the form > > {User, Password}. > > Where both User and Password should be strings. The > .yaws_auth > file mechanism is not (yet) recursive. Thus any > subdirectories > to Dir are not automatically also protected. > > > string, the user and password must be strings. > As for the deprecatedness, I honestly don't remember > why this was deprecated. > > Seems to naive me, that having the user/pass data in the > different directories is possibly better than having > it yaws.conf > > It really ought to be recursive as well. > > /klacke > |