On 7/9/07, Eric Pugh <[EMAIL PROTECTED]> wrote:
My patch for adding rich unstructured content (https://
issues.apache.org/jira/browse/SOLR-284) has a problem when some of
the extra field data passed in via the get request have spaces etc..
The content comes through URL encoded.
Should the SolrParams object handle decoding of parameters, or should
that be the domain of my RichDocumentRequestHandler since only some
parameters will have URL encoding.
Anhy URL encoding should already be automatically decoded by the time
the handler gets any data via SolrParams. Or was it double-encoded
perhaps?
-Yonik