Re: Forms require that the request method be POST and that the t:formdata query parameter have values.

I added this solution to the FAQ: https://tapestry.apache.org/specific-errors-faq.html If anyone has a better solution (until TAP5-1733 is fixed), please share... On Jan 18, 2016 5:44 PM, "Bob Harner" wrote: > This probably deserves to be added to Tapestry's FAQ page. It's quite > common with T

Re: Forms require that the request method be POST and that the t:formdata query parameter have values.

This probably deserves to be added to Tapestry's FAQ page. It's quite common with Tapestry apps. If your app is on a publicly site then it is a common result of bots crawling your site and submitting any forms that they finds. If it isn't on a public site then it may be a browser (e.g. certain ver

Re: Forms created in a loop - problem with validation

I think this is caused by the field being reused in the loop. You might need to recordError with a FieldSnapshot. Example here http://t5stitch-lazan.rhcloud.com/mapbindingdemo

Re: Forms created in a loop - problem with validation

These examples might help... If you’re not using AJAX then it probably makes more sense to put the Form around the Loop: T5.4: http://jumpstart.doublenegative.com.au/jumpstart7/examples/tables/editableloop1

Re: Forms require that the request method be POST and that the t:formdata query parameter have values

On Fri, Feb 20, 2015 at 11:47 AM, Charles Karow wrote: > We got a lot of these a few months ago, and in every case they were from > the then-current version of Chrome: > > Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) > Chrome/39.0.2171.71 Safari/537.36 > > At the tim

Re: Forms require that the request method be POST and that the t:formdata query parameter have values

We got a lot of these a few months ago, and in every case they were from the then-current version of Chrome: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36 At the time I interviewed a few of the users, who were using the auto-fill

Re: Forms require that the request method be POST and that the t:formdata query parameter have values

Digging deeper, looking at the form src. I'm seeing the following ex String[] values = request.getParameters(FORM_DATA); if (!request.getMethod().equals("POST") || values == null) throw new RuntimeException(messages.format("core-invalid-form-request", FORM_DATA)); Is there any way to know which

Re: Forms require that the request method be POST and that the t:formdata query parameter have values

I also found this article related to android. Again I'm not very familiar with this stuff, so please forgive me if it's unrelated. http://stackoverflow.com/questions/8587913/what-exactly-does-urlconnection-setdooutput-affect On Fri, Feb 20, 2015 at 11:04 AM, George Christman wrote: > Some furth

Re: Forms require that the request method be POST and that the t:formdata query parameter have values

Some further research has turned up this http://stackoverflow.com/questions/8187188/android-4-0-ics-turning-httpurlconnection-get-requests-into-post-requests I also posted the following question on SO http://stackoverflow.com/questions/28632632/browser-turning-a-post-request-into-a-get?noredirect

Re: Forms require that the request method be POST and that the t:formdata query parameter have values

On Fri, Feb 20, 2015 at 9:31 AM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Fri, 20 Feb 2015 12:15:55 -0200, George Christman < > gchrist...@cardaddy.com> wrote: > > So the question is how is the user able to force the browser to load that >> url in the address bar, "I assumin

Re: Forms require that the request method be POST and that the t:formdata query parameter have values

On Fri, 20 Feb 2015 12:15:55 -0200, George Christman wrote: So the question is how is the user able to force the browser to load that url in the address bar, "I assuming its being loaded in the address bar"? Is there a bug in the form component or could the user have some sort of browser sett

Re: Forms require that the request method be POST and that the t:formdata query parameter have values

Most likely a bot crawling your site. You may choose to suppress this logging for crawlers. This can be done by maintaining a list of crawler user agents and checking the user agent request header before logging.

Re: Forms require that the request method be POST and that the t:formdata query parameter have values

Hi, That could be an autocomplete feature of browser's address bar -- which autocompletes form's submission URL. Or it could be that user submits a form and it takes too long to process it, and during that time user clicks to browser's address bar and hits Enter (which issues HTTP GET request).

Re: Forms require that the request method be POST

That depends on if the page containing the form and/or form handlers @RequiresAuthentication or @RequiresUser. On Wed, Jun 25, 2014 at 10:49 PM, George Christman wrote: > Okay cool, that works too. Now if I'm setting remember me to true, should I > still be seeing this exception? > > > On Wed,

Re: Forms require that the request method be POST

Okay cool, that works too. Now if I'm setting remember me to true, should I still be seeing this exception? On Wed, Jun 25, 2014 at 2:44 PM, Dmitry Gusev wrote: > It won't continue form submission, user will be redirected to the page with > empty form. > > > On Wed, Jun 25, 2014 at 10:31 PM, Ge

Re: Forms require that the request method be POST

It won't continue form submission, user will be redirected to the page with empty form. On Wed, Jun 25, 2014 at 10:31 PM, George Christman wrote: > Thanks Dmitry, I'm willing to give it a shot. What outcome should I expect > to see from your code? Will it just bring the user back to a blank for

Re: Forms require that the request method be POST

Thanks Dmitry, I'm willing to give it a shot. What outcome should I expect to see from your code? Will it just bring the user back to a blank form, or will it continue with the form submission? On Wed, Jun 25, 2014 at 1:56 PM, Dmitry Gusev wrote: > Hi George, > > See one possible solution here:

Re: Forms require that the request method be POST

Hi George, See one possible solution here: https://github.com/tynamo/tapestry-security/issues/7#issuecomment-40301795 On Wed, Jun 25, 2014 at 7:36 PM, George Christman wrote: > So I finally figured out how to reproduce this exception. I'm using > Tapestry-Security and if the session times out

Re: Forms require that the request method be POST

So I finally figured out how to reproduce this exception. I'm using Tapestry-Security and if the session times out and the user submits the form, the page is redirected to the login page. When the user logs in, it attempts to resubmit the form and ends with this exception. Does anybody know how to

Re: Forms require that the request method be POST

Thanks for the tips guys, I'll see if I can find the culprit now that I know why it's happening. On Mon, May 19, 2014 at 5:52 PM, Eugen wrote: > Hi, I have had this kind of exception then i tried to submit a form > programmatically from an Applet (HttpClient) without sending the > formData fiel

Re: Forms require that the request method be POST

Hi, I have had this kind of exception then i tried to submit a form programmatically from an Applet (HttpClient) without sending the formData field. 2014-05-19 22:31 GMT+02:00 Kristian Marinkovic : > Hi, > > check if it is the same client. i once had the same problem. After several > hours of inve

Re: Forms require that the request method be POST

Hi, check if it is the same client. i once had the same problem. After several hours of investigation it was a developer with a browser plugin (web developer) which enabled converting form post requests to get requests. hope this helps. g, Kris On Mon, May 19, 2014 at 5:55 PM, George Christman

Re: Forms require that the request method be POST

Let me do some more homework now that I at least now how it's thrown. Thanks Thiago. On Mon, May 19, 2014 at 10:54 AM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Mon, 19 May 2014 11:44:06 -0300, George Christman < > gchrist...@cardaddy.com> wrote: > > In this particular case

Re: Forms require that the request method be POST

On Mon, 19 May 2014 11:44:06 -0300, George Christman wrote: In this particular case the application sits behind a firewall with no public access so I don't believe this is bot activity. Do you have any other thoughts? Do you have any information on when this exception actually happens? O

Re: Forms require that the request method be POST

In this particular case the application sits behind a firewall with no public access so I don't believe this is bot activity. Do you have any other thoughts? On May 19, 2014 10:00 AM, "Thiago H de Paula Figueiredo" wrote: > On Mon, 19 May 2014 09:37:44 -0300, George Christman < > gchrist...@card

Re: Forms require that the request method be POST

On Mon, 19 May 2014 09:37:44 -0300, George Christman wrote: Hi Everyone, I'm using 5.4 and I've continued to randomly see this exception popup in multiple applications. I'm wondering what it means and how to fix it. Thanks. Very probably bots crawling your site. -- Thiago H. de Paula Figue

Re: Forms require that the request method be POST and that the t:formdata query parameter have values.

I'm sure there are GET requests from search bots. Make sure you exclude action/event links and form actions in robots.txt (like Disallow: /*?t:ac=*, Disallow: */pagename.component:action* 02.12.2013 17:41, Ben Titmarsh пишет: Hi Guys, I'm getting quite a lot of these exceptions in my logs.

Re: Forms require that the request method be POST and that the t:formdata query parameter have values

See http://tapestry.1045711.n5.nabble.com/Safari-for-example-browser-history-and-form-exception-td4942074.html On 08/12/2012, at 10:09 PM, Muhammad Gelbana wrote: > I think this error occurs when you visit a similar url (through a GET > request, just by putting the following address in the bro

Re: Forms require that the request method be POST and that the t:formdata query parameter have values

I think this error occurs when you visit a similar url (through a GET request, just by putting the following address in the browser's address bar and hitting enter): http://localhost/pagename.formid This url is the "action" attribute value for the form element. It should be using within an http P

Re: Forms - BeanEditor and t:select

It seams that your *add="descriptionCreator" + * is right way. Now is everything OK. Thank you very much for help and for fast replay. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Forms-tp2427184p5713583.html Sent from the Tapestry - User mailing list archive at Nabble.c

Re: Forms - BeanEditor and t:select

I do that in this way: 2012/6/1 stipenovi > Can anyone help me: > > I have 2 entities: Description and Person with unidirectional ManyToOne > mapped relationship. > Every description must have descriptionCreator (Person). > > I have this code in tml: > > >

Re: Forms - BeanEditor and t:select

Can anyone help me: I have 2 entities: Description and Person with unidirectional ManyToOne mapped relationship. Every description must have descriptionCreator (Person). I have this code in tml: I injected SelectModelFactory, and have SelectModel as @Property in page class. I also created Per

Re: Forms and JavaScriptSupport

That was all with my problem. Thanks Taha for all the help. If somebody wants the code: *Class:* Object onSuccess(){ ... if (request.isXHR()) { ajaxResponseRenderer.addCallback(new JavaScriptCallback() { @Override public void run(JavaScriptSupport arg0) { arg0.addScript(String.forma

Re: Forms and JavaScriptSupport

In that case you can use ajaxResponseRenderer for closing the colorbox on form submission and then redirect the main window in the close event of colorbox(using js or ajax). On May 18, 2012, at 12:27 AM, Juan Alba wrote: > I *need* to redirect. > > The idea is the following: > My page has a b

Re: Forms and JavaScriptSupport

I *need* to redirect. The idea is the following: My page has a button to add xxx. Whe I click this, it opens the modal with the form. When I fill in the form and submit, it is redirecting to the page but in the modal, I need to close the modal and redirect the "main" page. I am clear or is really

Re: Forms and JavaScriptSupport

If you redirecting , no JavaScript will run. If you want colorbox to close and you stay on the same page don't redirect. If you want to redirect then why to close the colorbox. Sent from my iPhone On May 18, 2012, at 12:09 AM, Juan Alba wrote: > Taha, thanks Again but still can't make it wo

Re: Forms and JavaScriptSupport

Taha, thanks Again but still can't make it work. I have this now: *tml:* ${message:name} in the *class* Object onSuccess(){ if (request.isXHR()) { ajaxResponseRenderer.addCallback(new JavaScriptCallback() { @Override public void run(JavaScriptSupport arg0) {

Re: Forms and JavaScriptSupport

It has to be an ajax request for ajaxResponseRenderer to work. Also, for an ajax request if you want to redirect return an instance of Link from the event handler. return pageRenderLinkSource.createPageRenderLink(ShowRoutePlan.class); regards Taha On May 17, 2012, at 11:25 PM, Juan Alba wrote

Re: Forms and JavaScriptSupport

Taha, thanks a lot for your help but I am not sure if I am doing it right. I added this as you told me: @Inject private AjaxResponseRenderer ajaxResponseRenderer; Object onSuccess(){ ... ajaxResponseRenderer.addCallback(new JavaScriptCallback() { @Override public void run(JavaScriptSu

Re: Forms and JavaScriptSupport

Hi You can't use JavaScriptSupport directly from environment in action phase but you can do this @Inject private AjaxResponseRenderer ajaxResponseRenderer; Object onSuccess(){ ... ajaxResponseRenderer.addCallback(new JavaScriptCallback() { @Override public void run(Ja

Re: Forms require that the request method be POST....

Ok, I will try it in my code. Thanks Lenny! -- David Germán Canteros 2012/3/20 Lenny Primak > I am the author of that fix and it definitely works correctly. > It strips out the form from the request and redirects it to the page tha

Re: Forms require that the request method be POST....

I am the author of that fix and it definitely works correctly. It strips out the form from the request and redirects it to the page that the client was actually looking for. On Mar 20, 2012, at 9:04 AM, David Canteros wrote: > Hi guys! > Lately I detected a lot of this exception in the logs of my

Re: Forms require that the request method be POST....

I forgot to say that I'm using tapestry 5.3.2 running on tomcat 6, and the exceptions happens which users who use Firefox 3... -- David Germán Canteros 2012/3/20 David Canteros > Hi guys! > Lately I detected a lot of this excepti

Re: Forms plus none tapestry fields

Thanks for the tip! That component looks awsame and I made a test and compare it with Erich Hynd's multiselect which also is god. I ran into some javascript issues in my minimal test page that I will try to solve this evening. It was some god old conflict between prototype / jquery but I think. I

Re: Forms plus none tapestry fields

Taha has done a blogpost on a component that sounds like what you are looking for. In this blogpost ( http://tawus.wordpress.com/2011/12/28/multivalue-autocomplete-for-tapestry) he creates a component based on this library http://loopj.com/jquery-tokeninput/ Cheers, Lance. On Saturday, 3 March 2

Re: Forms plus none tapestry fields

On Sat, 03 Mar 2012 12:32:00 -0300, Gunnar Eketrapp wrote: Hi! Hi, Gunnar! Caused by: org.apache.tapestry5.ioc.util.UnknownValueException: Could not find a coercion from type java.lang.String to type utskicket.model.entity.MemberList. I guess the problem itself is that you're putting a

Re: Forms

On Thu, 16 Feb 2012 08:58:30 -0200, stipenovi wrote: I will post here... This is my simple code: * t:inPlace="false" t:id="multiBeanForm" t:zone="editorZone"> * t:id="createForm" t:object="nodeTop" t:zone="editorZone" t:exclude="id, version, nodeLevel, level,

Re: Forms

I will post here... This is my simple code: * t:inPlace="false" t:id="multiBeanForm" t:zone="editorZone"> * t:id="createForm" t:object="nodeTop" t:zone="editorZone" t:exclude="id, version, nodeLevel, level, dateCreated"/> * t:id="createDescriptionForm" t:object="de

Re: Forms and Grid questions ....

On Tue, 28 Dec 2010 07:09:36 -0200, Gunnar Eketrapp wrote: Hi! Hi! My questions are: 1) How do I disable the sorting functionality of the grid. Matheus answered that. :) 2) If I would like to suppport sorting and paging then I need some way to first submit what's been checked. I gue

Re: Forms and Grid questions ....

Hi, Gunnar! I think I know how to answer your first question. I assume your are using Tapestry 5.2.4 as I am. :-) You need to create an explicit BeanModel, customize its sorting funcionality and provide it to your Grid component. *Page class* @Inject private BeanModelSource beanModelSource

Re: Forms

I expected to see them inside the text fields On Fri, Jan 16, 2009 at 10:45 AM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > Em Fri, 16 Jan 2009 08:35:54 -0300, Sid Ferreira > escreveu: > > I was losing the values anyway... >> > > Ooops. I forgot to say that you should return nul

Re: Forms

Em Fri, 16 Jan 2009 08:35:54 -0300, Sid Ferreira escreveu: I was losing the values anyway... Ooops. I forgot to say that you should return null instead of this. And I just can't see why you say you're losing the fields values, as in no place in your code you print them in HTML nor the sta

Re: Forms

I was losing the values anyway... On Fri, Jan 16, 2009 at 10:13 AM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > Em Thu, 15 Jan 2009 16:58:10 -0300, Sid Ferreira > escreveu: > > Object onSuccess() { >> //new Exception("E..." + dsQuery).printStackTrace(); >> retu

Re: Forms

Em Thu, 15 Jan 2009 16:58:10 -0300, Sid Ferreira escreveu: Object onSuccess() { //new Exception("E..." + dsQuery).printStackTrace(); return this; } Never return "this" in a event handler method. This leads to loss of field values when they are not persisted in the

Re: Forms

Em Fri, 16 Jan 2009 05:59:00 -0300, Peter Stavrinides escreveu: As far as I know you can use a standard submit button. You're absolutely correct. I *never* used the Submit component, and I'm writing Tapestry 5 applications since 5.0.5 (almost two years ago). :) By the way, you don't nee

Re: Forms

additional terms relating to this e-mail. - Original Message - From: "Sid Ferreira" To: "Tapestry users" Sent: Friday, 16 January, 2009 10:46:11 AM GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: Forms in the end I managed a different way: created a pdsQue

Re: Forms

in the end I managed a different way: created a pdsQuery with @Persist and onSuccess dsQuery sets pdsQuery and it worked. But looks too lame. In jumpstart Geoff used a common submit. Also: is there a way to after the submit hide the Start? Keep it in server.ext/app/ ? On Fri, Jan 16, 2009 at 6:

Re: Forms

hi sid, you need to use a Tapestry Submit component to submit the form. otherwise the request wont be processed by Tapestry g, kris Sid Ferreira 15.01.2009 20:58 Bitte antworten an "Tapestry users" An Tapestry users Kopie Thema Forms Guys, Im trying to make a small search engine