You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Konrad Slepoy (JIRA)" <ji...@apache.org> on 2015/04/13 20:47:12 UTC
[jira] [Updated] (SOLR-7386) Ability to Circumvent Content-Type
Requirement
[ https://issues.apache.org/jira/browse/SOLR-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Slepoy updated SOLR-7386:
--------------------------------
Description:
There is no way to circumvent a content-type requirement for a POST request.
This came about because my team passes a POST request body which should not be touched by SOLR and is used by our native application. However, with the new inclusions in SOLR/Heliosearch it seems like SOLR tries to parse the body in a new way.
was:
There is no way to circumvent a content-type requirement for a request.
This came about because my team passes a POST request body which should not be touched by SOLR and is used by our native application. However, with the new inclusions in SOLR/Heliosearch it seems like SOLR tries to parse the body in a new way.
> Ability to Circumvent Content-Type Requirement
> ----------------------------------------------
>
> Key: SOLR-7386
> URL: https://issues.apache.org/jira/browse/SOLR-7386
> Project: Solr
> Issue Type: Improvement
> Reporter: Konrad Slepoy
>
> There is no way to circumvent a content-type requirement for a POST request.
> This came about because my team passes a POST request body which should not be touched by SOLR and is used by our native application. However, with the new inclusions in SOLR/Heliosearch it seems like SOLR tries to parse the body in a new way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org