couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Uday Jarajapu <>
Subject Re: Couchdb error when posting document - 413 Request entity too large
Date Fri, 03 Feb 2012 03:30:20 GMT
Hello Mark,

I was able to capture traffic between my localhost and couchDB while
writing a document that resulted in 413. Looking at the traffic with a
simple display filter set (ip.dst == <ip_of_couchdb>) , I could not see any
big difference that jumped out at me.

The only thing missing was a final ACK during this run. Is there a set
pattern that I should watch out for ?


On Tue, Jan 17, 2012 at 3:44 PM, Uday Jarajapu <>wrote:

> Thanks Mark. I will try this out and update you if I find something
> interesting.
> On Jan 17, 2012, at 3:34 PM, Mark Hahn wrote:
> > I use tcpdump on linux and then analyze the results in windows using
> > wireshark.  Wireshark has a bit of a learning curve but I think it is
> worth
> > it.  So far every time I've gotten an error from couch at this level it
> > turned out to be bad on the wire and was ultimately my fault.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message