From 665f32302f80265e29ed0f8f850dabfc3dc1f07d Mon Sep 17 00:00:00 2001 From: "http://smcv.pseudorandom.co.uk/" Date: Tue, 18 Feb 2014 11:08:28 -0400 Subject: [PATCH] note httpauth weirdness --- .../How_can_I_invert_the_banned__95__user_check__63__.mdwn | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/doc/forum/How_can_I_invert_the_banned__95__user_check__63__.mdwn b/doc/forum/How_can_I_invert_the_banned__95__user_check__63__.mdwn index d53a78682..2436b2e56 100644 --- a/doc/forum/How_can_I_invert_the_banned__95__user_check__63__.mdwn +++ b/doc/forum/How_can_I_invert_the_banned__95__user_check__63__.mdwn @@ -26,3 +26,8 @@ PS: the user is authenticated via 'httpauth', would that make a difference? > --[[smcv]] >> That was my initial setup but it wasn't working and I got caught-up on the `banned_user` idea. It would seem I was getting tricked by some credential-caching-weirdness. Fired up another browser and `locked_pages` works perfectly. Thanks. -- fergus + +>>> Browsers generally remember HTTP auth credentials until they're closed +>>> or get a 401 error, and don't generally have a way to "log out". +>>> As far as I'm aware, there's nothing that [[plugins/httpauth]] can +>>> do about that. --[[smcv]]