Aseem,
is this still relevant? I get the HTTP error with

POST /db/data/ext/CypherPlugin/graphdb/execute_query {"query": "START
n=(0) RETURN n.foobar"}

Cheers,

/peter neubauer

GTalk:      neubauer.peter
Skype       peter.neubauer
Phone       +46 704 106975
LinkedIn   http://www.linkedin.com/in/neubauer
Twitter      http://twitter.com/peterneubauer

http://www.neo4j.org               - Your high performance graph database.
http://startupbootcamp.org/    - Ă–resund - Innovation happens HERE.
http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party.


On Tue, Aug 30, 2011 at 7:59 AM, Aseem Kishore <aseem.kish...@gmail.com>wrote:

> Hey,
>
> Just ran into an HTML error response which broke our error handling code
> since it was expecting the body to be JSON. It seems to only happen with
> the
> Cypher plugin. Here's a simple repro -- just paste this into the HTTP
> console in the web admin:
>
> POST /db/data/ext/CypherPlugin/graphdb/execute_query {"query": "START
> n=(0) RETURN n.foobar"}
>
> Assuming a node w/ ID 0 exists, and assuming it has no "foobar" property,
> this should return an HTML error.
>
> Let me know if my assumption here that errors should always be JSON is an
> incorrect one! We've worked around this for now, but just reporting as a
> bug.
>
> Cheers,
> Aseem
> _______________________________________________
> Neo4j mailing list
> User@lists.neo4j.org
> https://lists.neo4j.org/mailman/listinfo/user
>
_______________________________________________
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user

Reply via email to