Uploaded image for project: 'Tapestry'
  1. Tapestry
  2. TAPESTRY-1605

The request encoding (for component action requests) occurs too late; after query parameters of the request have been accessed, which prevents the proper request encoding from being used

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.5
    • Fix Version/s: 5.0.11
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      Due to changeset 550147 that fix issue "tapestry-1294",

      request.setCharacterEncoding is not working in case of form submit data event
      because of method request.setEncoding in RequestEncodingInitializerImpl is called after
      request.getParameter(InternalConstants.PAGE_CONTEXT_NAME) in ComponentActionDispatcher.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                hlship Howard M. Lewis Ship
                Reporter:
                pphetra polawat phetra
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: