[jira] Updated: (SOLR-443) POST queries don't declare its charset

2008-07-02 Thread Lars Kotthoff (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kotthoff updated SOLR-443: --- Attachment: SOLR-443-multipart.patch Attaching new patch which makes it configurable through a

[jira] Updated: (SOLR-443) POST queries don't declare its charset

2008-07-02 Thread Lars Kotthoff (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kotthoff updated SOLR-443: --- Attachment: (was: SOLR-443-multipart.patch) POST queries don't declare its charset

[jira] Updated: (SOLR-443) POST queries don't declare its charset

2008-06-18 Thread Lars Kotthoff (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kotthoff updated SOLR-443: --- Attachment: SOLR-443-multipart.patch After reading

[jira] Updated: (SOLR-443) POST queries don't declare its charset

2008-03-12 Thread Hiroaki Kawai (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiroaki Kawai updated SOLR-443: --- Attachment: SolrDispatchFilter.patch This patch will fix the issue. New in Servlet Spec 2.5, we can

[jira] Updated: (SOLR-443) POST queries don't declare its charset

2007-12-21 Thread Andrew Schurman (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schurman updated SOLR-443: - Attachment: solr-443.patch Simple fix that will fix the issue for this case. I don't believe it

[jira] Updated: (SOLR-443) POST queries don't declare its charset

2007-12-21 Thread Ryan McKinley (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-443: --- Attachment: solr-443.patch Andrew, does this patch work for you? rather then specify the contentType