[
https://issues.apache.org/jira/browse/SOLR-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Siebel updated SOLR-4110:
---------------------------------
Attachment: SOLR-4110_trunk.patch
SOLR-4110_branch_4x.patch
Patch to make Content-Type header configurable in PHPResponseWriters.
Had to add two patches for trunk and branch_4x separately, due to changes in
trunk ("missing @Overrides").
> 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
> Assignee: Mark Miller
> Priority: Minor
> Labels: 4.0.1_Candidate
> Fix For: 4.1, 5.0
>
> Attachments: SOLR-4110_branch_4x.patch, SOLR-4110.patch,
> SOLR-4110_trunk.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: [email protected]
For additional commands, e-mail: [email protected]
