receiving 400 codes when the http log says it's sending 200 OK

[Wes Freeman]

New to dispatch/reboot, so I could be confused or doing something wrong here, but dispatch seems like it's getting error codes when it shouldn't be.

I'm using dispatch synchronously via apply(), and this 400 code has been weirdly intermittent--shifting around between different tests. That's what apply() should do, right--force it to wait for the request to complete?

Any ideas?

Thanks,

Wes

Full code is here, if you want to see how the request gets made: https://github.com/AnormCypher/AnormCypher/blob/master/src/main/scala/anormcypher/Neo4jREST.scala#L29

[info] - should be able to make a query without parameters *** FAILED ***

[info]   java.util.concurrent.ExecutionException: dispatch.StatusCode: Unexpected response status: 400

[info]   at com.ning.http.client.providers.netty.NettyResponseFuture.abort(NettyResponseFuture.java:297)

[info]   at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.abort(NettyAsyncHttpProvider.java:1326)

[info]   at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.access$700(NettyAsyncHttpProvider.java:137)

[info]   at com.ning.http.client.providers.netty.NettyAsyncHttpProvider$HttpProtocol.handle(NettyAsyncHttpProvider.java:2274)

[info]   at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.messageReceived(NettyAsyncHttpProvider.java:1128)

[info]   at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:75)

[info]   at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)

[info]   at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:792)

[info]   at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:141)

[info]   at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)

[info]   ...

[info]   Cause: dispatch.StatusCode: Unexpected response status: 400

[info]   at dispatch.OkHandler$class.onStatusReceived(handlers.scala:37)

[info]   at dispatch.OkFunctionHandler.onStatusReceived(handlers.scala:29)

[info]   at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.updateStatusAndInterrupt(NettyAsyncHttpProvider.java:1462)

[info]   at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.access$2100(NettyAsyncHttpProvider.java:137)

[info]   at com.ning.http.client.providers.netty.NettyAsyncHttpProvider$HttpProtocol.handle(NettyAsyncHttpProvider.java:2227)

[info]   at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.messageReceived(NettyAsyncHttpProvider.java:1128)

[info]   at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:141)

[info]   at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)

[info]   at org.jboss.netty.handler.codec.replay.ReplayingDecoder.unfoldAndFireMessageReceived(ReplayingDecoder.java:600)

[info]   at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:584)

[Wes Freeman]

Ok, so I think the problem is not with dispatch, but rather the logging system, which seems to be reporting 200 status even when it is sending errors. :(

Anyway, I'm glad (at least I think) that my dispatch stuff isn't where the problem is coming from.

Wes