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

Form input not correctly decoded in case of non-english charsets

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 5.0.13
    • 5.0.14
    • None
    • None

    Description

      This problem occurs because major browsers don't conform to standards which says that client charset should be sent via "content-type" HTTP header to server.
      Everything is well described in this article:
      http://www.crazysquirrel.com/computing/general/form-encoding.jspx

      I guess this is closely related to submitted issue:
      https://issues.apache.org/jira/browse/TAPESTRY-915

      So, fix should be that
      HttpServletRequest.setEncodingCharset("UTF-8"); (I guess charset should be configurable somehow)
      is set in tapestry filter prior to anyone fetching any parameter value.

      Attachments

        Issue Links

          Activity

            People

              hlship Howard Lewis Ship
              vjeran@tis.hr Vjeran Marcinko
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Slack

                  Issue deployment