: > but I can't see an easy way to be able to pass a cookie with the request. : > The cookie is needed to be able to get through the SSO layer but will just
Unless i'm remembering wrong, and HttpClient instance will manage cookies for you, so why not just document how your users can use an HttpClient instance to talk to a server that will set this cookie, and then reuse that HttpClient instance in your CommonsHttpSolrServer instance. : > be ignored by Solr. I see that you are using Apache Commons Http Client and : > with that I would be able to write the cookie if I had access to the : > HttpMethod being used (GetMethod or PostMethod). However, I can not find an : > easy way to get access to this with SolrJ and thought I would ask before : There's no easy way I think. You can extend CommonsHttpSolrServer and : override the request method. Copy/paste the code from : CommonsHttpSolrServer#request and make the changes. It is not an elegant way : but it will work. If he really needs to hardcode the cookie value into code, wouldn't it be easier to extend HttpClient and modify the methods which take in an HttpMethod object to first set the cookie on those obejcts before delegating to super? -Hoss
