Hi!
Sorry if this is a known bug…
Under webrt, after creating a new request, you get the just created
request shown.
When using the reload button in Netscape in this situation you create
the same request again with a new Request-Number.
This mustn’t happen…
Thanks for your work!
Michael
ps: please keep the work on the mail-frontend up. Some real hacker
admins try only to use this (they don’t like netscape…).
When using the reload button in Netscape in this situation you create
the same request again with a new Request-Number.
with a form-based CGI, pressing the ‘reload’ button on a CGI form
re-submits your form data. rt sounds like it is doing the right thing
there.
not that there aren’t ways around it, i just wanted to point out that it’s
broken by design. 
Blue Lang Unix Systems Admin
QSP, Inc., 3200 Atlantic Ave, Ste 100, Raleigh, NC, 27604
Home: 919 835 1540 Work: 919 875 6994 Fax: 919 872 4015
RT does a FORM POST to send the data to the server.
If you relaod the create-a-ticket page, you’re going to
see that behavior. I’ve got some ideas for how to guard against
users doing this in the future…On Tue, Jul 25, 2000 at 06:11:45PM +0200, Michael Moellney wrote:
Hi!
Sorry if this is a known bug…
Under webrt, after creating a new request, you get the just created
request shown.When using the reload button in Netscape in this situation you create
the same request again with a new Request-Number.This mustn’t happen…
Thanks for your work!
Michael
ps: please keep the work on the mail-frontend up. Some real hacker
admins try only to use this (they don’t like netscape…).
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
jesse reed vincent — root@eruditorum.org — jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
“Mary had a crypto key / She kept it in escrow
And everything that Mary said / The Feds were sure to know” – Sam Simpson
When using the reload button in Netscape in this situation you create
the same request again with a new Request-Number.This mustn’t happen…
Hm … I’d almost say like Bill Gates, this is a user error, not a design
error. We’ve used post forms, that means data actually is posted to the
webserver. Most browsers pop up with a warning about this to the user.
Anyway, I guess you have a point here; maybe it might be an idea to put a
bit clearer warning at the document. I’ll think about that for RT2. Ehm.
My fork of it, at least
Spell checkers are for wimps
(please send feedback on all typos)