lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dennis Gearon <gear...@sbcglobal.net>
Subject Re: Non-English query via Solr Example Admin corrupts text
Date Thu, 20 May 2010 22:33:53 GMT
<rant_by_HTTP_Verb_Nazi>

Using POST totally violates the access model for an entity in the HTTP Verb model.

Basically:

GET=READ
POST=CREATE
PUT=MODIFY
DELETE=(drum roll please)DELETE

Granted, the whole web uses POST for modify, but let's not make the situation worse by using
it for everything.

</rant_by_HTTP_Verb_Nazi>

Dennis Gearon

Signature Warning
----------------
EARTH has a Right To Life,
  otherwise we all die.

Read 'Hot, Flat, and Crowded'
Laugh at http://www.yert.com/film.php


--- On Thu, 5/20/10, Chris Hostetter <hossman_lucene@fucit.org> wrote:

> From: Chris Hostetter <hossman_lucene@fucit.org>
> Subject: Re: Non-English query via Solr Example Admin corrupts text
> To: solr-user@lucene.apache.org
> Date: Thursday, May 20, 2010, 11:40 AM
> 
> : I am using apache-solr-1.4.0.war deployed to glassfishv3
> on my 
>     ...
> : INFO: [] webapp=/apache-solr-1.4.0 path=/select 
> :
> params={indent=on&version=2.2&q=numéro&fq=&start=0&rows=10&fl=*,score&qt=standard&wt=standard&explainOther=&hl.fl=}
> 
> : hits=0 status=0 QTime=16
>     ...
> : In my SolrJ using application, I have a test case which
> queries for 
> : "numéro" and succeeds if I use Embedded and fails if I
> use 
> : CommonsHttpSolrServer... I don't want to use embedded for
> a number of 
>     ...
> : I am sorry if you'd dealt with this issue in the past,
> I've spent a few 
> : hours googling for solr utf-8 query and glassfishv3 utf-8
> uri plus other 
> : permutations/combinations but there were seemingly
> endless amounts of 
> : chaff that I couldn't find anything useful after scouring
> it for a few 
> : hours.  I can't decide whether it's a glassfish
> issue or not so I am not 
> : sure where to direct my energy.  Any tips or advice
> are appreciated!
> 
> I suspect if you switched to using POST instead of GET your
> problem would 
> go away -- this stems from amiguity in the way HTTP
> servers/browsers deal 
> with encoding UTF8 in URLs.  a quick search for
> "glassfish url encoding" 
> turns up this thread...
> 
>   http://forums.java.net/jive/thread.jspa?threadID=38020
> 
> which refreneces...
> 
> http://wiki.glassfish.java.net/Wiki.jsp?page=FaqHttpRequestParameterEncoding
> 
> ...it looks like you want to modify the "default-charset
> attribute of the 
> <parameter-encoding>"
> 
> 
> -Hoss
> 

Mime
View raw message