Re: gnatsweb and cookies

[Jason Molenda]

Yeah, this approach has worked pretty well.  If the client doesn't
provide an existing cookie, we assume they're a read-only user
(guest/guest on this system) by default.  If they want to authenticate,
they have to manually go to the Login screen.  Given that most
read/write users will only need to do this one time, it is the
appropriate burden of effort.

Because new/non-cookie-accepting users aren't run through the Login
screen the default, they can get by without cookies.

I wrote this little patch a while back and I may be mis-remembering
some of the details of its effects, but that's the gist of it.

Jason


On Fri, Mar 15, 2002 at 04:42:21PM +0100, Gerald Pfeifer wrote:

> Actually, it seems surprisingly simple. ;-) Below you'll find a patch due
> to Jason Molenda (CC:ed) which we have been using on gcc.gnu.org; some-
> thing similiar for use with current GNATS/gnatsweb should be relatively
> simple, I guess.
> 
> Gerald
> 
> Index: gnatsweb.pl
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/cgi-bin/gnatsweb.pl,v
> retrieving revision 1.49
> retrieving revision 1.50
> diff -u -3 -p -r1.49 -r1.50
> --- gnatsweb.pl 2001/12/18 21:11:00     1.49
> +++ gnatsweb.pl 2001/12/19 07:22:34     1.50
> @@ -3501,6 +3501,13 @@ sub main
>    $global_prefs{'database'}="gcc";
>    #GCC-LOCAL end.
> 
> +  #GCC-LOCAL begin: No username/pass provided?  Default to guest/guest
> +  if (!$db_prefs{'user'} || !$db_prefs{'password'}) {
> +    $db_prefs{'user'} = "guest";
> +    $db_prefs{'password'} = "guest";
> +  }
> +  #GCC-LOCAL end.
> +
>    # Big old switch to handle commands.
>    if($cmd eq 'store query')
>    {