Hi Furkan, If you are using trunk, or a version of MCF that you have sources for, you might want to add logging statements to ModifiedHttpSolrClient.createMethod(), to see what HTTP method it is choosing and why it is choosing it. Once we figure that we can make whatever changes are needed to make it use POST again.
Maybe the problem is that there's no body stream at all, and there's only metadata. If that is the case it may choose to use GET. It would be easy to change that behavior though. Please let me know. Thanks, Karl On Thu, Mar 2, 2017 at 10:20 AM, Karl Wright <[email protected]> wrote: > What version of ManifoldCF is this? There was a recent integration with a > 6.x version of SolrJ -- I wonder if that now uses GET instead of POST? If > that's true, I can't see how that would work. > > Karl > > On Thu, Mar 2, 2017 at 10:13 AM, Furkan KAMACI <[email protected]> > wrote: > >> Hi Karl, >> >> Single Solr instance is set and "Use the Extract Update Handler:" is >> clicked. Also, Update handler is /update/extract >> >> Kind Regards, >> Furkan KAMACI >> >> On Thu, Mar 2, 2017 at 3:52 PM, Karl Wright <[email protected]> wrote: >> >>> Hi Furkan, >>> >>> The error is coming from Solr. How is your Solr connection configured? >>> If you are using /update/extract, your documents should be sent via POST, >>> not GET. >>> >>> Karl >>> >>> >>> On Thu, Mar 2, 2017 at 8:24 AM, Furkan KAMACI <[email protected]> >>> wrote: >>> >>>> Hi, >>>> >>>> When I test E-mail connector I get that error: >>>> >>>> Error from server at http://localhost:8983/solr/collection1: non ok >>>> status: 414, message:Request-URI Too Long >>>> >>>> As far as I know, such kind of errors are get at HTTP GET operations >>>> and E-mail connector operations may have long URLs. Is it possible to avoid >>>> that error? >>>> >>>> Kind Regards, >>>> Furkan KAMACI >>>> >>> >>> >> >
