Re: intermittent stack trace

2013-08-23 Thread Ilya Obshadko
I guess there's a cleaner way to do the same thing. In addition, page request context is being preserved: https://gist.github.com/xfyre/a8aab5ff9428961b252f On Sat, Mar 23, 2013 at 3:56 PM, Geoff Callender < geoff.callender.jumpst...@gmail.com> wrote: > See > http://apache-tapestry-mailing-list

Re: intermittent stack trace

2013-03-24 Thread Bob Harner
I've also seen this error when a form submission takes so long to return that users get frustrated and click into URL field of the browser and hit Enter. This submits the URL as a GET instead of a POST. On Mar 22, 2013 1:59 PM, "Ken in Nashua" wrote: > Hi Folks, > > Could I get some input on this

RE: intermittent stack trace

2013-03-23 Thread Ken in Nashua
Thanks Geoff... I added clientValidation=false on my form definition and that caused it to stop before I even asked about this.. ... I was alarmed it happened on my live site. So I am a bit stale on what can happen to live sites. Not sure what could be going on under the hood... but I

Re: intermittent stack trace

2013-03-22 Thread Geoff Callender
See http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/Safari-for-example-browser-history-and-form-exception-td4942074.html . Geoff On 23/03/2013, at 5:15 AM, Thiago H de Paula Figueiredo wrote: > On Fri, 22 Mar 2013 14:59:15 -0300, Ken in Nashua wrote: > >> Forms require tha

Re: intermittent stack trace

2013-03-22 Thread Thiago H de Paula Figueiredo
On Fri, 22 Mar 2013 14:59:15 -0300, Ken in Nashua wrote: Forms require that the request method be POST and that the t:formdata query parameter have values. Here is, from the error message, the description of what is happening. If this is a public-facing site, your probably have someone c