-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andreas,
Andreas Prieß wrote: > I think the HTTP spec says that there should be _no_ change of status > performed on a GET request - GET should alwasy be repeatable without > danger. While I think you're right, and agree in general, my UI makes the most sense with links in this case. It turns out that this really isn't happening. I must have been hallucinating. In any event, I may decide to switch to buttons. I dunno... > For actions like yours, that's what other HTTP commands like > POST and PUT are for. AFAIK, there's no way to instruct a browser to do a PUT request, especially not in a standard link. > Even search engines will trigger actions if such a page is public. Or > think of someone setting up a local search engine also... That's why these pages are neither public nor searchable ;) - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGF6h19CaO5/Lv0PARAsBkAKCMGjN1uX+6F6BKbMoFs3pvZPZ43gCgjZD0 vlfJoOFEITJ3iC/1E3Srw+Y= =xM4h -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
