Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Message-ID: <1994561513.109571264703494701.JavaMail.jira@brutus.apache.org>
Date: Thu, 28 Jan 2010 18:31:34 +0000 (UTC)
From: "Claudio Valente (JIRA)" <jira@apache.org>
To: solr-dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-1603) Perl Response Writer
In-Reply-To: <1003495952.1259179839698.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806016#action_12806016 ] 

Claudio Valente commented on SOLR-1603:
---------------------------------------

Network corruption or malicious tampering with data (from Solr to the client) could result in injected code being executed.

All I'm trying to say is that this is by no means a new concern for the perl output writer alone.

If you do need tests to merge this please read my paragraph regarding that and tell me whether there are others that I'm missing.

> Perl Response Writer
> --------------------
>
>                 Key: SOLR-1603
>                 URL: https://issues.apache.org/jira/browse/SOLR-1603
>             Project: Solr
>          Issue Type: New Feature
>          Components: Response Writers
>            Reporter: Claudio Valente
>            Priority: Minor
>         Attachments: SOLR-1603.patch
>
>
> I've made a patch that implements a Perl response writer for Solr.
> It's nan/inf and unicode aware.
> I don't know whether some fields can be binary but if so I can probably extend it to support that.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.