[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-users] Using a NULL cookieStore to suppress unparseable cookie logging
|
Hi,
On Tue, Apr 28, 2015 at 8:33 PM, Bradley Wagner
<bradley.wagner@xxxxxxxxxxxxxx> wrote:
>
> Hi, we’ve built a link checker using Jetty’s HttpClient and we’re trying to suppress SEVERE error logging that we’re seeing as a result of unparseable cookies (see below). Basically, we’re not interested in cookies at all. I saw in Java’s CookieManager that we could bypass this code if the cookieStore was NULL but I don’t see any way to set a NULL cookieStore on Jetty’s HttpClient since it validates it non-null on set.
>
> Any clever workarounds or suggestions on how we could use a NULL cookieStore or otherwise suppress this error? Thanks!
httpClient.setCookieStore(new HttpCookieStore.Empty());
sets a no-operation cookie store that does not parse nor store them.
That good ?
--
Simone Bordet
----
http://cometd.org
http://webtide.com
http://intalio.com
Developer advice, training, services and support
from the Jetty & CometD experts.
Intalio, the modern way to build business applications.
