[
https://issues.apache.org/jira/browse/WICKET-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070985#comment-15070985
]
ASF subversion and git services commented on WICKET-6050:
---------------------------------------------------------
Commit 1d9c6b955553d72e36b029e44bc07e3206fa4e88 in wicket's branch
refs/heads/wicket-6.x from [~mgrigorov]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=1d9c6b9 ]
WICKET-6050 Wicket Ajax (Wicket.From.serializeElement) causes 400 bad request
WICKET-5948 wicket-ajax.js probably doesn't traverse the children of <div> or
<span>
WICKET-6006 ModalWindow.closeCurrent() causes 414 status error
Introduce AjaxRequestAttributes#serializeRecursively with default value 'false'.
This is a flag indicating whether to collect (submit) the name/value pairs for
all HTML form elements children of the HTML element with the JavaScript listener
> 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
> Assignee: Martin Grigorov
> 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)
