Since we only use go.php now when not using cookies, this is much less 
of an issue.

I don't have any good suggestions on how to handle it.  Like I said, I 
understand why the check is there but it hampers the use of some of 
Horde's own modules features.  Security and useability are often at 
odds with each other.

I'm open to suggestions, if you like. Consider the case of an image in 
an html email that deletes your calendar, vs. the attend.php links. 
Should we just make a big ugly list of things we might link to in 
Horde? I sure don't want to maintain it....

Hrm.. that leaves me at an impasse.  I want people to use Horde.  And 
I want people to heed warnings on links that make scary (to them) 
warning statements :)  And for once, some of them are actually heeding 
the warning.



That really puts a damper on using linked attachments though.

There is no way we can do this without rewriting all of Horde to 
ensure that no destructive action can ever occur on a GET. That's a 
reasonable long-term goal, though...

On two occasions now, Horde has generated Potentially Dangerous URL 
warnings - when clicking on Kronolith attend.php links from IMP, and 
when clicking on linked attachments links from IMP.  I understand the 
idea behind the warning but it would be helpful if Horde treated 
things like linked attachments and Kronolith attend.php links as "safe".