On the other hand, POST is the wrong HTTP semantic for a search request and makes it impossible to use HTTP caching. POST also makes all your requests look identical in the HTTP logs, so you can't do any log analysis.
If GET works, always use GET. wunder On 6/17/09 9:18 AM, "Erik Hatcher" <e...@ehatchersolutions.com> wrote: > > On Jun 17, 2009, at 12:01 PM, Brian_K wrote: > >> >> Is it possible to query /select using http POST rather than GET? Is >> the >> syntax different it so? >> >> When I try, I receive an 500 response and a big fat exception. >> >> java.lang.NullPointerException >> at java.io.StringReader.<init>(Unknown Source) >> at org.apache.lucene.queryParser.QueryParser.parse(QueryParser.java: >> 169 > > Yes, POST works fine... I think you just missed providing the q > parameter, which is required in the most basic case. > > Erik >
