Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    12.0p: Content-Type Request header of exportClientData missing charset-parameter

    Hi Isomorphic,

    if you compare normal IDACall requests like the one here with the exportClientData one here, you'll notice these headers in the F12 browser tools (using v12.0p_2020-06-13):
    • normal:
      Content-Type: application/x-www-form-urlencoded; charset=UTF-8
    • exportClientData:
      Content-Type: application/x-www-form-urlencoded
    We had a web.xml change that also involved some filters. Apparently Tomcat only reads parameters once and the encoding has to be matching then. It does not help to set it afterwards (see #6 in these Tomcat docs). This change broke exportClientData for us.
    According to the servlet docs having the charset=UTF-8 explicitly in the request would have solved the issue for us as well. We fixed it now like this in the web.xml with an 1st filter:

    Code:
        <filter>
            <description>Tomcat Set Character Encoding filter</description>
            <filter-name>SetCharacterEncodingFilter</filter-name>
            <filter-class>org.apache.catalina.filters.SetCharacterEncodingFilter</filter-class>
            <init-param>
                <param-name>encoding</param-name>
                <param-value>UTF-8</param-value>
            </init-param>
        </filter>
        <filter-mapping>
            <filter-name>SetCharacterEncodingFilter</filter-name>
            <url-pattern>/app/sc/IDACall/*</url-pattern>
        </filter-mapping>
    I assume that the header is just missing here as other requests do have it. If so, can you add it here as well?

    Thank you & Best regards
    Blama

    #2
    Hi Isomorphic,

    I just realized this also applies to the exportData() requests in this sample, where this leads to scrambled Umlauts in criteria.

    Best regards
    Blama

    Comment


      #3
      Hi Isomorphic,

      can you have a look at this one?

      Best regards
      Blama

      Comment


        #4
        Apologies for the delay, we're looking into this and will follow up soon.

        Comment

        Working...
        X