Strictly you still need the 2nd parameter. I don't know any browser 
that doesn't support relative path redirections, but it's not official 
HTTP standard.

When I  started refactoring I thought that legacy action handling must 
be done only in one or two places and that it will be easier. But now 
I'm convinced that migration script probably would have been a better 
idea. Will prepare a patch later.
Does adding redirect() automatically assumes that URL is full and I 
don't need second parameter? Or do I still need Horde::url('foo.php', 
true)->redirect() ?

- I've seen a few cases where you handle legacy lowercase action 
names. How about adding a migration instead to ucfirst the actions in 
the forms table once and for all?
- You can simplify redirection by using Horde::url('foo.php')->redirect()

Changes have been made in Git for this ticket:

No need to re-throw (Request #10326).

  1 files changed, 1 insertions(+), 5 deletions(-)
http://git.horde.org/horde-git/-/commit/4212a9bb30c6031df21b9ff4d855713648ebbe18

Changes have been made in Git for this ticket:

private -> protected (Request #10326).

  1 files changed, 1 insertions(+), 1 deletions(-)
http://git.horde.org/horde-git/-/commit/9765febfa01bbb960639ea80032e75009de2b9e2

Main changes:

* Fixed Mailto action driver to use Horde_Mime_Mail().
* PEAR_Error -> Exceptions.
* Horde_Util::addParameter -> Horde::url.
* Autoloading.
* OOP fixes.

I still have Horde_Template -> Horde_View patch to work on, but 
hopefully after that Ulaform can be released as beta.