[
https://issues.apache.org/jira/browse/SOLR-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-1940:
---------------------------
Attachment: SOLR-1940.patch
Lance: can you try this patch out on your websphere server and see if it fixes
the problem?
(FWIW: I think websphere has a bug in this respect - the servlet spec says
"This method may be called repeatedly to change content type" and for
getContentType it says "If no content type has been specified, this method
returns null." .. since there is no oher way to "clear" the contentType
property on the ServletResponse object, it seems like it should definitley be
valid to pass null to setContentType)
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
