Any workarounds until the fix is released? Using curl.
On Wed, Dec 11, 2019 at 1:52 PM Martynas Jusevičius <[email protected]> wrote: > > https://issues.apache.org/jira/browse/JENA-1795 > > On Wed, Dec 11, 2019 at 1:31 PM Andy Seaborne <[email protected]> wrote: > > > > Hi Martynas, > > > > Could you raise a ticket please? > > > > Andy > > > > On 11/12/2019 09:53, Martynas Jusevičius wrote: > > > Hi, > > > > > > I would expect the same response status and headers for GET and HEAD, > > > minus the body. However GET returns 200 and HEAD 400: > > > > > > GET /ds/ HTTP/1.1 > > > Host: localhost:3030 > > > User-Agent: curl/7.47.0 > > > Accept: */* > > > > > > HTTP/1.1 200 OK > > > Date: Wed, 11 Dec 2019 09:49:11 GMT > > > Fuseki-Request-ID: 6 > > > Vary: Accept,Accept-Encoding,Accept-Charset > > > Content-Type: text/trig > > > Transfer-Encoding: chunked > > > > > > > > > HEAD /ds/ HTTP/1.1 > > > Host: localhost:3030 > > > User-Agent: curl/7.47.0 > > > Accept: */* > > > > > > HTTP/1.1 400 Neither default graph nor named graph specified > > > Date: Wed, 11 Dec 2019 09:42:49 GMT > > > Fuseki-Request-ID: 5 > > > Vary: Accept,Accept-Encoding,Accept-Charset > > > Content-Type: text/plain;charset=utf-8 > > > Cache-Control: must-revalidate,no-cache,no-store > > > Pragma: no-cache > > > Content-Length: 59 > > > > > > Is that expected? > > >
