Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-443

POST queries don't declare its charset

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 1.2
    • 1.3
    • clients - java
    • None
    • Tomcat 6.0.14

    Description

      When sending a query via POST, the content-type is not set. The content charset for the POST parameters are set, but this only appears to be used for creating the Content-Length header in the commons library. Since a query is encoded in UTF-8, the http headers should also specify content type charset.

      On Tomcat, this causes problems when the query string contains non-ascii characters (characters with accents and such) as it tries to parse the POST body in its default ISO-9886-1. There appears to be no way to set/change the default encoding for a message body on Tomcat.

      Attachments

        1. solr-443.patch
          2 kB
          Ryan McKinley
        2. solr-443.patch
          1 kB
          Andrew Schurman
        3. SOLR-443-multipart.patch
          7 kB
          Lars Kotthoff
        4. SolrDispatchFilter.patch
          0.5 kB
          Hiroaki Kawai

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            aschurman Andrew Schurman
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment