From: Jason Molenda <jason-gnatslist@molenda.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: help-gnats@gnu.org, Dirk Bergstrom <dirk@juniper.net>,
Michael Richardson <mcr@sandelman.ottawa.on.ca>
Subject: Re: gnatsweb and cookies
Date: Fri, 15 Mar 2002 09:04:00 -0000 [thread overview]
Message-ID: <20020315090247.A14189@molenda.com> (raw)
In-Reply-To: <Pine.BSF.4.44.0203151639370.21128-100000@naos.dbai.tuwien.ac.at>; from pfeifer@dbai.tuwien.ac.at on Fri, Mar 15, 2002 at 04:42:21PM +0100
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')
> {
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2002-03-15 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 11:34 Michael Richardson
2002-03-12 13:00 ` Dirk Bergstrom
2002-03-15 8:20 ` Gerald Pfeifer
2002-03-15 9:04 ` Jason Molenda [this message]
2002-03-21 14:54 ` Michael Richardson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020315090247.A14189@molenda.com \
--to=jason-gnatslist@molenda.com \
--cc=dirk@juniper.net \
--cc=help-gnats@gnu.org \
--cc=mcr@sandelman.ottawa.on.ca \
--cc=pfeifer@dbai.tuwien.ac.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).