Hi diddier, Nevermind. I figured it out. There was some miscommunication between me and our IT guy.
Thanks for helping. It's fixed now. Alexandre On Thu, Aug 19, 2010 at 9:59 AM, Alexandre Rocco <alel...@gmail.com> wrote: > Hi diddier, > > I have updated my etc/jetty.xml and updated my headerBufferSize to 2x as: > <Set name='headerBufferSize'>16384</Set> > > But the error persists. Do you know if there is any other config that > should be updated so this setting works? > Also, is there any way to check if jetty is use this config inside Solr > admin pages? I know that we can check the Java properties but I haven't > found any way to locate the jetty config there. > > Thanks! > Alexandre > > On Wed, Aug 18, 2010 at 4:58 PM, didier deshommes <dfdes...@gmail.com>wrote: > >> Hi Alexandre, >> Have you tried setting a higher headerBufferSize? Look in >> etc/jetty.xml and search for 'headerBufferSize'; I think it controls >> the size of the url. By default it is 8192. >> >> didier >> >> On Wed, Aug 18, 2010 at 2:43 PM, Alexandre Rocco <alel...@gmail.com> >> wrote: >> > Guys, >> > >> > We are facing an issue executing very large query (~4000 bytes in the >> URL) >> > in Solr. >> > When we execute the query, Solr (probably Jetty) returns a HTTP 413 >> error >> > (FULL HEAD). >> > >> > I guess that this is related to the very big query being executed, and >> > currently we can't make it short. >> > Is there any configuration that need to be tweaked on Jetty or other >> > component to make this query work? >> > >> > Any advice is really appreciated. >> > >> > Thanks! >> > Alexandre Rocco >> > >> > >
