I'll add a test with rows = 0 and see how easy it is to replicate. Looks to me like you should file a JIRA issue in any case.
- Mark On Mar 14, 2013, at 2:04 PM, yriveiro <yago.rive...@gmail.com> wrote: > Hi, > > I think that in solr 4.2 the new feature to proxy a request if the > collection is not in the requested node has a bug. > > If I do a query with the parameter rows=0 and the node doesn't have the > collection. If the parameter is rows=4 or superior then the search works as > expected > > the curl returns > > The output of wget is: > > Connecting to 192.168.20.48:8983... connected. > HTTP request sent, awaiting response... 200 OK > Length: 210 [application/xml] > Saving to: ‘select?q=*:*&rows=0’ > > 0% [ > > ] 0 --.-K/s in 0s > > 2013-03-14 18:01:04 (0.00 B/s) - Connection closed at byte 0. Retrying. > > Curl says: > > curl > "http://192.168.20.48:8983/solr/ST-3A856BBCA3_12/select?q=*%3A*&rows=0"; > curl: (56) Problem (2) in the Chunked-Encoded data > > Chrome says: > > This webpage is not available > The webpage at > http://192.168.20.48:8983/solr/ST-3A856BBCA3_12/select?q=*%3A*&rows=0&wt=xml&indent=true > might be temporarily down or it may have moved permanently to a new web > address. > Error 321 (net::ERR_INVALID_CHUNKED_ENCODING): Unknown error. > > Someone have the same issue? > > > > > > ----- > Best regards > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-4-2-mechanism-proxy-request-error-tp4047433.html > Sent from the Solr - User mailing list archive at Nabble.com.
