Hmm.. Maybe I should be more explicit.
Here's the warning: > Oct 05 09:13:47 WARN [pool-2-thread-16] httpclient.HttpMethodBase - > Cookie rejected: "$Version=0; > _twitter_sess > =BAh7CjoRdHJhbnNfcHJvbXB0MDoOcmV0dXJuX3RvIh5odHRwOi8vdHdpdHRl > %250Aci5jb20vamJuaW5kOgxjc3JmX2lkIiUxNmI1MDIwZjk5ZDY4NDg3OWZhZTIz > %250AMWY2M2I2ZWQxMjoHaWQiJTQ4YmM1NmU2Nzc1ZWYwZWY1ZDVkMGFhMGMxYjQw > %250AMjI2IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hI > %250AYXNoewAGOgpAdXNlZHsA--2cf7d8d6a5a619808fe1676a801b0ecfc8cc2aec; > $Path=/; $Domain=.twitter.com". Illegal domain attribute > ".twitter.com". Domain of origin: "twitter.com" I doubt I'll get twitter to change there page. :) How would I write a policy that dealt with this? D/ On Oct 5, 2009, at 4:21 AM, sebb wrote: > On 05/10/2009, Douglas Ferguson <[email protected]> wrote: >> I"m using HttpClient from apache commons >> >> I get of bunch of these warnings in my logs. >> >> I could set HttpmethodBase to INFO but I'd be worried that I'd loose >> some useful information. >> Is there something else I could do to avoid these messages? >> >> Oct 04 20:49:22 WARN [pool-2-thread-5] httpclient.HttpMethodBase - >> Cookie rejected: " > > FInd out why the cookie is being rejected, and either fix the cookie > to be compliant, or configure HttpClient to use a cookie policy that > allows the cookie. > >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
