Hi, FYI. Here's a modified version of the sesame http client module that now issues dumb accept headers ( only SPARQL XML ). It is an effective workaround for the CN glitch if you're experiencing it while using sesame HTTPRepository.
Install this in your maven local repo (overwrite the old jar) and REMEMBER to clean it later on when this issue is fixed. Don't seed it in any repos beyond your local as it is a hack and I didn't change the version number. Thanks, A On Fri, May 22, 2009 at 1:25 PM, Kingsley Idehen <kide...@openlinksw.com> wrote: > Aldo Bucchi wrote: >> >> Hi Ivan, >> >> Thanks I'll check this workaround. >> BTW - These are the headers generated internally by the Sesame >> HTTPRepository client. >> > > We'll fix this matter. > > Kingsley >> >> Regards, >> A >> >> Sent from my iPhone >> >> On May 22, 2009, at 11:18 AM, Ivan Mikhailov <imikhai...@openlinksw.com> >> wrote: >> >> >>> >>> Hello Aldo, >>> >>> It seems to me that we have problem with multiple Accept: lines in the >>> HTTP header. If I swap two lines and send >>> >>> Accept: application/sparql-results+xml;q=0.8 >>> Accept: application/x-binary-rdf-results-table >>> Accept: application/xml;q=0.8 >>> >>> then it works. (I don't know whether it should return an empty >>> result-set but it does not produce an error.) >>> >>> I hope that the fix will come quickly. >>> >>> Best Regards, >>> >>> Ivan Mikhailov >>> OpenLink Software >>> http://virtuoso.openlinksw.com >>> >>> >>> On Thu, 2009-05-21 at 22:33 -0400, Aldo Bucchi wrote: >>> >>>> >>>> Hi, >>>> >>>> On Tue, May 19, 2009 at 6:25 PM, Kingsley Idehen <kide...@openlinksw.com >>>> >>>>> >>>>> wrote: >>>>> Aldo Bucchi wrote: >>>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> I am receiving an HTTP error when querying lod.openlinksw.com/ sparql >>>>>> The query is valid SPARQL, trust me. This appears to be a CN error of >>>>>> some >>>>>> kind. >>>>>> >>>>>> >>>>>> POST /sparql HTTP/1.1 >>>>>> Content-Type: application/x-www-form-urlencoded; charset=utf-8 >>>>>> Accept: application/x-binary-rdf-results-table >>>>>> Accept: application/sparql-results+xml;q=0.8 >>>>>> Accept: application/xml;q=0.8 >>>>>> User-Agent: Jakarta Commons-HttpClient/3.1 >>>>>> Host: lod.openlinksw.com >>>>>> Content-Length: 662 >>>>>> >>>>>> >>>>>> >>>>>> queryLn=SPARQL&query=SELECT+%3Fvalue+WHERE+%7B+%3Chttp%3A%2F%2Fwww.univrz.com >>>>>> %2Fdataspace%2Fperson%2Faldo.bucchi%23this%3E+%3Fp+%3Fvalue+. >>>>>> +FILTER%28+%3Fp+%3D+%3Chttp%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf- >>>>>> schema%23label%3E+%7C%7C+%3Fp+%3D+%3Chttp%3A%2F%2Fdbpedia.org >>>>>> %2Fproperty%2Fname%3E+%7C%7C+%3Fp+%3D+%3Chttp%3A%2F%2Fxmlns.com >>>>>> %2Ffoaf%2F0.1%2Fname%3E+%7C%7C+%3Fp+%3D+%3Chttp%3A%2F%2Fpurl.org >>>>>> %2Fdc%2Felements%2F1.1%2Ftitle%3E+%7C%7C+%3Fp+%3D+%3Chttp%3A%2F >>>>>> %2Frdfs.org%2Fsioc%2Fns%23name%3E+%7C%7C+%3Fp+%3D+%3Chttp%3A%2F%2Fwww.w3.org >>>>>> %2F2005%2FAtom%23title%3E+%7C%7C+%3Fp+%3D+%3Chttp%3A%2F%2Fwww.w3.org >>>>>> %2F2004%2F02%2Fskos%2Fcore%23label%3E+%29+%7D+LIMIT+1&infer=true >>>>>> >>>>>> >>>>>> >>>>>> HTTP/1.1 406 Unacceptable >>>>>> Server: Virtuoso/06.00.3119 (Linux) x86_64-unknown-linux-gnu VDB >>>>>> Connection: Keep-Alive >>>>>> Content-Type: text/html; charset=UTF-8 >>>>>> Date: Tue, 19 May 2009 21:43:24 GMT >>>>>> Accept-Ranges: bytes >>>>>> Alternates: {"sparql" 1 {type application/sparql-results+xml} >>>>>> {charset >>>>>> UTF-8} {length 292}} >>>>>> Content-Length: 383 >>>>>> >>>>>> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> >>>>>> <html><head> >>>>>> <title>406 Not Acceptable</title> >>>>>> </head><body> >>>>>> <h1>406 Not Acceptable</h1> >>>>>> <p>An appropriate representation of the requested resource sparql >>>>>> could not be found on this server.</p> >>>>>> Available variant(s): >>>>>> <ul> >>>>>> <li><a href="sparql">sparql</a> , type application/sparql-results >>>>>> +xml, >>>>>> charset UTF-8</li> >>>>>> </ul> >>>>>> </body></html> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> Yes, it looks like a transparent content negotiation glitch introduced >>>>> by >>>>> the latest binary behind that instance :-( >>>>> >>>>> Anyway, we'll double check. >>>>> >>>> >>>> I can confirm we now introduced this bug to a V5 instance when >>>> upgrading, so it is most probably something recent. >>>> This kills our SPARQLing clients, thus rendering our apps unusable. >>>> >>>> Yikes! >>>> >>> >>> >> >> >> ------------------------------------------------------------------------------ >> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT >> is a gathering of tech-side developers & brand creativity professionals. >> Meet >> the minds behind Google Creative Lab, Visual Complexity, Processing, & >> iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian >> Group, R/GA, & Big Spaceship. http://www.creativitycat.com >> _______________________________________________ >> Virtuoso-users mailing list >> Virtuoso-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/virtuoso-users >> >> > > > -- > > > Regards, > > Kingsley Idehen Weblog: http://www.openlinksw.com/blog/~kidehen > President & CEO OpenLink Software Web: http://www.openlinksw.com > > > > > -- Aldo Bucchi U N I V R Z Office: +56 2 795 4532 Mobile:+56 9 7623 8653 skype:aldo.bucchi http://www.univrz.com/ http://aldobucchi.com/ PRIVILEGED AND CONFIDENTIAL INFORMATION This message is only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If you are not the intended recipient, please do not distribute or copy this communication, by e-mail or otherwise. Instead, please notify us immediately by return e-mail. INFORMACIÓN PRIVILEGIADA Y CONFIDENCIAL Este mensaje está destinado sólo a la persona u organización al cual está dirigido y podría contener información privilegiada y confidencial. Si usted no es el destinatario, por favor no distribuya ni copie esta comunicación, por email o por otra vía. Por el contrario, por favor notifíquenos inmediatamente vía e-mail.
sesame-http-client-2.2.4.jar
Description: application/java-archive
