That particular exception is quite a bane for it happens a lot on live
public sties when they're crawled by various bots, and the logs fill
up quick! (Along with the IllegalArgException thrown when the URL
contains spaces.)
That said, I don't believe it is up to Tapestry to make exceptions to
the rule and handle these cases any differently. T5 is being strict
and believe that to be right, otherwise where do you draw the line?
What I would like to see, however, are more bespoke exceptions being
thrown so I can more easily identify them in my exception handling
Currently, my code reads something like:
if (exception.getMessage().contains("Forms require that the request
method be POST") {
doRedirect();
}
which is brittle and nasty. I'd much rather have:
if (exception instanceof MalformedContextUrl) {
doRedirect();
}
Steve.
On 27 October 2011 14:21, Lenny Primak <lpri...@hope.nyc.ny.us> wrote:
> Safari has a friendly (overly friendly) URL completion, and it picks up
> Tapestry forms,
> which gives an ugly exception:
>
> For example for when I start typing pallet, the url URL
> https://www.XXX.com/stage/test/palletpage.srch.searchform comes
> up from the previous history.
> An unexpected application exception has occurred.
>
> Forms require that the request method be POST and that the t:formdata query
> parameter have values.
>
>
> Is there any way to prevent this or make an exception friendlier?
> For example, I am pretty sure that GET method is never valid on a form,
> so this should redirect to the actual page.
>
> What do you guys think?
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
