You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jena.apache.org by "Neubert, Joachim" <J....@zbw.eu> on 2017/04/25 08:34:38 UTC

ResponseProcessCookies warnings

In a federated query with values already bound, it seems that I get for each bound value an entry in the fuseki log:

[2017-04-24 19:43:33] ResponseProcessCookies WARN  Invalid cookie header: "Set-Cookie: WMF-Last-Access=24-Apr-2017;Path=/;HttpOnly;secure;Expires=Fri, 26 May 2017 12:00:00 GMT". Invalid 'expires' attribute: Fri, 26 May 2017 12:00:00 GMT
[2017-04-24 19:43:33]     : "Set-Cookie: WMF-Last-Access-Global=24-Apr-2017;Path=/;Domain=.wikidata.org;HttpOnly;secure;Expires=Fri, 26 May 2017 12:00:00 GMT". Invalid 'expires' attribute: Fri, 26 May 2017 12:00:00 GMT

The (simplified) query was:

PREFIX wdt: <http://www.wikidata.org/prop/direct/>
select *
where {
  bind("118578537" as ?gndId)
  service <https://query.wikidata.org/bigdata/namespace/wdq/sparql> {
    ?wd wdt:P227 ?gndId .
  }
}

Stas Malyshev, the tech guy at wikidata, pointed out that the header should be correct (and is probably added by their Varnish, so this could bite in other places, too).

There seems to be a long-lasting issue with HttpClient in this respect (https://issues.apache.org/jira/browse/HTTPCLIENT-923), which perhaps is not completely fixed.

Since the warning may show up thousands and thousands of times (according to the number of bound values), it would be great if it could be fixed somehow.

Cheers, Joachim

Re: AW: ResponseProcessCookies warnings

Posted by Andy Seaborne <an...@apache.org>.

On 26/04/17 07:33, Neubert, Joachim wrote:
> Hi Andy,
>
>> Have you tried configuring the logging so that warnings from that class are
>> turned off?
>
> Thanks for the hint! I've tried change the log level in tomcat/conf/logging.properties, but neither
>
> 	org.apache.http.client.protocol.ResponseProcessCookies.level = SEVERE
> nor
> 	org.apache.http.client.protocol.ResponseProcessCookies.level = ERROR
>
> had any effect (after restart). Yet, that may have been the completely wrong place.
>
> Cheers, Joachim
>

What about log4j?  I think Fuseki has a tendency to end up using that. 
It uses the logging system of the webapp, not the tomcat server.

	Andy

ERROR isn't a level in java.util.logging.

AW: ResponseProcessCookies warnings

Posted by "Neubert, Joachim" <J....@zbw.eu>.
Hi Andy,

> Have you tried configuring the logging so that warnings from that class are
> turned off?

Thanks for the hint! I've tried change the log level in tomcat/conf/logging.properties, but neither

	org.apache.http.client.protocol.ResponseProcessCookies.level = SEVERE
nor
	org.apache.http.client.protocol.ResponseProcessCookies.level = ERROR

had any effect (after restart). Yet, that may have been the completely wrong place.

Cheers, Joachim

Re: ResponseProcessCookies warnings

Posted by Andy Seaborne <an...@apache.org>.
On 25/04/17 09:34, Neubert, Joachim wrote:
> In a federated query with values already bound, it seems that I get for each bound value an entry in the fuseki log:
>
> [2017-04-24 19:43:33] ResponseProcessCookies WARN  Invalid cookie header: "Set-Cookie: WMF-Last-Access=24-Apr-2017;Path=/;HttpOnly;secure;Expires=Fri, 26 May 2017 12:00:00 GMT". Invalid 'expires' attribute: Fri, 26 May 2017 12:00:00 GMT
> [2017-04-24 19:43:33]     : "Set-Cookie: WMF-Last-Access-Global=24-Apr-2017;Path=/;Domain=.wikidata.org;HttpOnly;secure;Expires=Fri, 26 May 2017 12:00:00 GMT". Invalid 'expires' attribute: Fri, 26 May 2017 12:00:00 GMT
>
> The (simplified) query was:
>
> PREFIX wdt: <http://www.wikidata.org/prop/direct/>
> select *
> where {
>   bind("118578537" as ?gndId)
>   service <https://query.wikidata.org/bigdata/namespace/wdq/sparql> {
>     ?wd wdt:P227 ?gndId .
>   }
> }
>
> Stas Malyshev, the tech guy at wikidata, pointed out that the header should be correct (and is probably added by their Varnish, so this could bite in other places, too).
>
> There seems to be a long-lasting issue with HttpClient in this respect (https://issues.apache.org/jira/browse/HTTPCLIENT-923), which perhaps is not completely fixed.
>
> Since the warning may show up thousands and thousands of times (according to the number of bound values), it would be great if it could be fixed somehow.
>
> Cheers, Joachim
>

Have you tried configuring the logging so that warnings from that class 
are turned off?

Th full class name is:

org.apache.http.client.protocol.ResponseProcessCookies

There isn't much else Fuseki can do without some serious replumbing 
(like creating our own logging to sit between slf4j and log4j or JUL).

	Andy