[ https://issues.apache.org/jira/browse/SOLR-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505695#comment-13505695 ]
Mark Miller commented on SOLR-4110: ----------------------------------- What about back compat? How might this affect those upgrading from 4.0? > Configurable Content-Type headers for PHPResponseWriters and > PHPSerializedResponseWriter > ---------------------------------------------------------------------------------------- > > Key: SOLR-4110 > URL: https://issues.apache.org/jira/browse/SOLR-4110 > Project: Solr > Issue Type: Improvement > Components: Response Writers > Affects Versions: 4.0 > Reporter: Dominik Siebel > Priority: Minor > Labels: 4.0.1_Candidate > Fix For: 4.1, 5.0 > > Attachments: SOLR-4110.patch > > > The *PHPResponseWriter* and *PHPSerializedResponseWriter* currently send a > hard coded Content-Type header of _text/plain; charset=UTF-8_ although there > are constants defining _text/x-php;charset=UTF-8_ and > _text/x-php-serialized;charset=UTF-8_ which remain unused. This makes content > type guessing on the client side quite complicated. > I already created a patch (from the branch_4x github branch) to use the > respective constants and also added the possibility to configure the > Content-Type header via solrconfig.xml (like in JSONResponseWriter). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org