You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Rakesh A (JIRA)" <ji...@apache.org> on 2015/12/14 09:53:46 UTC

[jira] [Updated] (WICKET-6050) Wicket Ajax (Wicket.From.serializeElement) causes 400 bad request

     [ https://issues.apache.org/jira/browse/WICKET-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rakesh A updated WICKET-6050:
-----------------------------
    Attachment: WICKET-5948-2.7z

Attached quick start

> Wicket Ajax (Wicket.From.serializeElement) causes 400 bad request
> -----------------------------------------------------------------
>
>                 Key: WICKET-6050
>                 URL: https://issues.apache.org/jira/browse/WICKET-6050
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 6.21.0
>            Reporter: Rakesh A
>         Attachments: WICKET-5948-2.7z
>
>
> Due to the recent change (WICKET-5948) in Wicket Ajax (JavaScript), Ajax calls add nested form element values as request parameters and result HTTP status code 400 when URL gets too long.
> This happens when you add an Ajax behavior (custom event triggered from JavaScript) to a DOM element with nested form fields.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)