They should probably be checked in unit tests within the Neo4j code base. I'll reopen the GitHub issue.
On 28 January 2014 15:35, Georg Summer <[email protected]> wrote: > On the topic of spotting: > org.apache.http.client does the spotting. > Caused by: org.apache.http.HttpException: Unsupported Content-Coding: UTF- > 8 > at org.apache.http.client.protocol.ResponseContentEncoding.process( > ResponseContentEncoding.java:98) > ... > > > While I do not have the time, one could make a small program that crawls > all URLs of an neo4j instance and checks for these exceptions. > > On Tuesday, 28 January 2014 16:03:44 UTC+1, Nigel Small wrote: > >> Yes, looks like that to me too. Good spot. Can someone from Neo confirm? >> >> >> On 28 January 2014 14:35, Georg Summer <[email protected]> wrote: >> >>> Sorry for dragging this post up but I think Neo4j 2.0 has the same >>> problem on the transaction rest endpoint >>> >>> curl -v -X POST http://localhost:7474/db/data/transaction >>> * About to connect() to localhost port 7474 (#0) >>> * Trying 127.0.0.1... >>> * Adding handle: conn: 0x100824000 >>> * Adding handle: send: 0 >>> * Adding handle: recv: 0 >>> * Curl_addHandleToPipeline: length: 1 >>> * - Conn 0 (0x100824000) send_pipe: 1, recv_pipe: 0 >>> * Connected to localhost (127.0.0.1) port 7474 (#0) >>> > POST /db/data/transaction HTTP/1.1 >>> > User-Agent: curl/7.32.0 >>> > Host: localhost:7474 >>> > Accept: */* >>> > >>> < HTTP/1.1 201 Created >>> < Location: http://localhost:7474/db/data/transaction/17 >>> < Content-Encoding: UTF-8 >>> < Content-Type: application/json >>> < Access-Control-Allow-Origin: * >>> < Transfer-Encoding: chunked >>> * Server Jetty(9.0.5.v20130815) is not blacklisted >>> < Server: Jetty(9.0.5.v20130815) >>> < >>> * Connection #0 to host localhost left intact >>> {"commit":"http://localhost:7474/db/data/transaction/17/commit >>> ","results":[],"transaction":{"expires":"Tue, 28 Jan 2014 14:31:20 >>> +0000"},"errors":[]} >>> >>> >>> On Monday, 15 July 2013 21:48:06 UTC+2, Nigel Small wrote: >>> >>>> No problem. To address a number of issues, I've rebuilt the entire >>>> HTTP/REST layer for py2neo and wrapped it up in a separate project ( >>>> https://github.com/nigelsmall/httpstream). This attempts to detect the >>>> correct encoding and automatically decode the content on the fly. This was >>>> the only reason I spotted it :-) >>>> >>>> Nige >>>> >>>> >>>> On 15 July 2013 17:44, Jim Webber <[email protected]> wrote: >>>> >>>>> Hey Nige, >>>>> >>>>> It'll be in the 1.9.2 release which, CI gods willing, will be out >>>>> tomorrow. Thanks for spotting it. >>>>> >>>>> Jim >>>>> >>>>> On 15 Jul 2013, at 15:48, Nigel Small <[email protected]> wrote: >>>>> >>>>> > That was quick! Thanks Peter :-) >>>>> > >>>>> > >>>>> > On 15 July 2013 15:30, Peter Neubauer <[email protected]> >>>>> wrote: >>>>> > Thanks Nige for reporting, seems it's fixed now. >>>>> > >>>>> > >>>>> > Cheers, >>>>> > >>>>> > /peter neubauer >>>>> > >>>>> > G: neubauer.peter >>>>> > S: peter.neubauer >>>>> > P: +46 704 106975 >>>>> > L: http://www.linkedin.com/in/neubauer >>>>> > T: @peterneubauer >>>>> > >>>>> > Kids in Malmö this summer? - http://www.kidscraft.se >>>>> > Neo4j questions? Use GraphGist. - http://gist.neo4j.org >>>>> > >>>>> > >>>>> > On Sat, Jul 13, 2013 at 1:29 PM, Nigel Small <[email protected]> >>>>> wrote: >>>>> > Hi chaps >>>>> > >>>>> > After spending an hour or so this morning trying to hunt down the >>>>> source of a Unicode problem, I've identified that there is a small HTTP >>>>> header issue that I've raised here: >>>>> > >>>>> > https://github.com/neo4j/neo4j/issues/961 >>>>> > >>>>> > To work around this, I'm going to adjust py2neo's default character >>>>> set to be UTF-8 and ignore the headers. Are there any circumstances under >>>>> which this wouldn't work? >>>>> > >>>>> > Cheers >>>>> > Nige >>>>> > >>>>> > >>>>> > -- >>>>> > You received this message because you are subscribed to the Google >>>>> Groups "Neo4j" group. >>>>> > To unsubscribe from this group and stop receiving emails from it, >>>>> send an email to [email protected]. >>>>> >>>>> > For more options, visit https://groups.google.com/groups/opt_out. >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > -- >>>>> > You received this message because you are subscribed to the Google >>>>> Groups "Neo4j" group. >>>>> > To unsubscribe from this group and stop receiving emails from it, >>>>> send an email to [email protected]. >>>>> >>>>> > For more options, visit https://groups.google.com/groups/opt_out. >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > -- >>>>> > You received this message because you are subscribed to the Google >>>>> Groups "Neo4j" group. >>>>> > To unsubscribe from this group and stop receiving emails from it, >>>>> send an email to [email protected]. >>>>> >>>>> > For more options, visit https://groups.google.com/groups/opt_out. >>>>> > >>>>> > >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Neo4j" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>>> >>>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Neo4j" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
