Hi Chris, Two things which may not necessarily be related:
1. Regarding HTTP POST, I dropped in the 'start.jar' from the 04-19-2006 build and still have the same error. Something as simple as this example should work, right? ---------- <HTML> <BODY> <form method="POST" action="http://localhost:8080/solr/select";> <input type="text" name="q" value="story_id:1"> <input type="submit" value="search"> </form> </BODY> </HTML> --------- Still getting the same error: <result status="1"> org.xmlpull.v1.XmlPullParserException: only whitespace content allowed before start tag and not q (position: START_DOCUMENT seen q... @1:1) 2. I can no longer 'ant compile'/'dist' the newest version(s) (04/16/06 - 04/19/06) of Solr due to the error: ------- [javac] /home/root/disks/src/solr-nightly/src/java/org/apache/solr/util/AbstractSolr TestCase.java:8: package junit.framework does not exist [javac] import junit.framework.TestCase; ... [javac] 6 errors [javac] 4 warnings ------- As well as a few other errors (with Sun's Java SDK 1.5.0_6). I previously ran 'ant compile'/'dist' on 04-07-2006 just fine -- am I missing any extra framework? I don't see this mentioned anywhere on the list so I'm guessing it's a problem on my end. Sorry if I'm missing something obvious here. Thanks again. Brian -----Original Message----- From: Chris Hostetter [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 19, 2006 1:03 PM To: solr-user@lucene.apache.org Subject: RE: Possible to HTTP POST (very long) queries? : Chris, thanks for the reply. I have an easy question: What's the syntax? : : Changing "GET" to "POST" in the form gives me: No special syntax, just regular old CGI form encoding -- just changing the GET to a POST in teh form should work okay. Are you sure you are using a nightly build from after April 7th? The exception you are getting looks like you are using an older build where all POSTs were interpreted as updates regardless of the URL. NOTE: if you are using Jetty, which the example setup does, there apears to be a slight bug because Jetty handles "empty" query params differnetly between GET and POST; I'll file an issue to track this as soon as Jira wakes up -- but the work arround is to make sure you don't include any options you don't need when you POST your query (ie: "stylesheet") -Hoss
