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 feature of the browser. I never was able to determine exactly what was happening, and have had to set the matter aside for other priorities.

On 2/20/15 11:27 AM, George Christman wrote:
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 one of these two conditions are actually
causing the exception? Can you still have a post while having null
form_data?

On Fri, Feb 20, 2015 at 11:09 AM, George Christman <gchrist...@cardaddy.com>
wrote:

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 <
gchrist...@cardaddy.com> wrote:

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=1#comment45565655_28632632

Someone answered with the following answer, I'm not sure if it even makes
sense.

The problem caused by address bar completion of all browsers and the
solution is that, please add *autocomplete="false"* to all of your forms.



On Fri, Feb 20, 2015 at 10:38 AM, George Christman <
gchrist...@cardaddy.com> wrote:


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 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 setting causing this. Ironically I noticed a lot of ie6 users
but
some android users as well which this exception. Before I block the
exception from clogging up my logs, I'd like to make one last attempt
at
resolving it.

What I'd really like to know is if the app is failing do to bad code
or if the user is doing something to cause it to fail.

I'd guess this is caused by browsers misbehaving, specially after the
IE6 info (who the hell still uses such an ancient and overall horrible
browser yet?). What else could turn a POST into a GET?

^^ lol, great question. I think I'm going to add a js warning for all xp
users to find an alternate browser. I didn't want to support old versions
of ie back then and I'm deff not doing it today lol.

Do you think there is a reason for a browser to do such a thing? I'm
assuming you don't believe it's bad code, but rather the browser screwing
up.

Some thoughts,

Relative urls shouldn't effect this right?

What about long transactions? Could a user stop, double submit etc that
could cause the browser to screw up?

--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



--
George Christman
CEO
www.CarDaddy.com
P.O. Box 735
Johnstown, New York



--
George Christman
CEO
www.CarDaddy.com
P.O. Box 735
Johnstown, New York



--
George Christman
CEO
www.CarDaddy.com
P.O. Box 735
Johnstown, New York





---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to