[
https://issues.apache.org/jira/browse/SOLR-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875812#action_12875812
]
Lance Norskog edited comment on SOLR-1940 at 6/4/10 8:53 PM:
-------------------------------------------------------------
The contentType parameters in index.jsp have no charset spec. On Windows this
defaulted to 8859-1.
I changed 'text/xml;charset=utf-8' to match the files. We could make the
default content type 'application/octet-stream' in ShowFileHandler.
Not tested on websphere.
was (Author: lancenorskog):
It has no charset spec. On Windows this defaulted to 8859-1 AKA USASCII.
I changed it to be text/xml;charset=utf-8 to match the files.
> SolrDispatchFilter sets content type as NULL
> --------------------------------------------
>
> Key: SOLR-1940
> URL: https://issues.apache.org/jira/browse/SOLR-1940
> Project: Solr
> Issue Type: Bug
> Reporter: Lance Norskog
> Attachments: SOLR-1940.patch, SOLR-1940.patch
>
>
> o.a.s.h.SolrDispatchFilter can set the output Content-Type to a null pointer
> instead of a string. Under websphere this results in a NullPointerException.
> This is the offending code:
> response.setContentType(responseWriter.getContentType(solrReq, solrRsp));
> Suggested fix: either use a default content type, or do not set the content
> type and let the browser handle it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
