Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-6050

Wicket Ajax (Wicket.From.serializeElement) causes 400 bad request

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 6.21.0
    • 7.2.0, 8.0.0-M1, 6.22.0
    • wicket
    • None

    Description

      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.

      Attachments

        1. WICKET-5948-2.7z
          147 kB
          Rakesh A

        Issue Links

          is broken by

          Improvement - An improvement or enhancement to an existing feature or task. WICKET-5948 wicket-ajax.js probably doesn't traverse the children of <div> or <span>

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          relates to

          Bug - A problem which impairs or prevents the functions of the product. WICKET-6006 ModalWindow.closeCurrent() causes 414 status error

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              mgrigorov Martin Tzvetanov Grigorov
              rakesh.a Rakesh A
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: