Hi Team, I'd like to unsubscribe from this group. Could you please help me out with this?
Regards, Sanjanaa -----Original Message----- From: Martynas Jusevičius <[email protected]> Sent: Friday, February 7, 2020 3:01 PM To: jena-users-ml <[email protected]> Subject: Re: Fuseki 3.13.0 GET vs HEAD CAUTION: External email, Please do not click links or open attachments unless you recognize the sender and know the content is safe. https://hub.docker.com/r/atomgraph/fuseki now uses 3.14.0. On Thu, Feb 6, 2020 at 11:03 AM Andy Seaborne <[email protected]> wrote: > > > > On 06/02/2020 09:33, Martynas Jusevičius wrote: > > Hmm, where are the binaries located? I have > > > > ARG VERSION=3.14.0 > > ARG SRC=http://central.maven.org/maven2/org/apache/jena/ > > ARG > > BINARY=jena-fuseki-server/${VERSION}/jena-fuseki-server-${VERSION}.j > > ar > > > > ENV > > URL=http://central.maven.org/maven2/org/apache/jena/jena-fuseki-serv > > er/${VERSION}/jena-fuseki-server-${VERSION}.jar > > > > but central.maven.org seems to be down :( > > The DNS entry for central.maven.org has gone away. > > There is https://repository.apache.org/content/repositories/releases > > The Jena build produces binary artifacts that get pushed there. That > is then mirrored to central. > > Or build locally. > > The "source-release" zip is the release. > For any Apache Software Foundation project a release is the source code. > The binaries are "convenience" (that everyone uses). > > For Jena, source-release and it is a copy of the GH repo master branch > at that point in time with the version set to the release version. > "mvn clean install" > > Or from git - the release is tagged, and the commit in the VOTE > message if you don't trust tagging. > > Or try: > > https://repo1.maven.org/maven2/ > > which is the real central. > > Andy > > > > > > > On Thu, Feb 6, 2020 at 10:17 AM Martynas Jusevičius > > <[email protected]> wrote: > >> > >> Missed this. Thanks! > >> > >> On Thu, Feb 6, 2020 at 10:16 AM Andy Seaborne <[email protected]> wrote: > >>> > >>> https://issues.apache.org/jira/browse/JENA-1795 > >>> > >>> Fix Version/s: > >>> Jena 3.14.0 > >>> > >>> https://www.apache.org/dist/jena/source/ > >>> jena-3.14.0-source-release.zip 2020-01-16 16:20 > >>> > >>> > >>> > >>> On 05/02/2020 23:33, Martynas Jusevičius wrote: > >>>> 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? > >>>>>>> ******************* CAUTION ******************* This e-mail is intended exclusively for the individual(s) to whom it is addressed and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, please notify the sender and delete the original message. Further, you are not to copy, disclose or disseminate this e-mail or the information contained to any other person and any such actions are unlawful. Zifo Technologies has taken every reasonable precaution to ensure that this e-mail and attachment(s) has been swept for viruses, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment(s). Zifo Technologies is neither liable for the proper and complete transmission of the information contained in this e-mail nor for any delay in its receipt. *************************************************
