From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/80537 Path: news.gmane.org!not-for-mail From: Steinar Bang Newsgroups: gmane.emacs.gnus.general Subject: Re: gnus-sync.el v2 Date: Sun, 06 Nov 2011 08:22:50 +0100 Organization: Probably a good idea Message-ID: <87hb2h4svp.fsf@dod.no> References: <87mxcv3fu2.fsf@lifelogs.com> <871uu1uh4e.fsf@dod.no> <874nyxm043.fsf@lifelogs.com> <87pqhicp6m.fsf@lifelogs.com> <87wrbqb4u8.fsf@lifelogs.com> <87lirw7w1d.fsf@dod.no> <8739e4q3uo.fsf@lifelogs.com> <87fwi47ryn.fsf@dod.no> <87obwsnkqv.fsf@lifelogs.com> <877h3f7gqk.fsf@dod.no> <87r51nmvr5.fsf@lifelogs.com> <87zkgb57kt.fsf@dod.no> <87mxcanbcv.fsf@lifelogs.com> <87vcqy6e59.fsf@dod.no> <87fwi2n2pt.fsf@lifelogs.com> <87mxca5uip.fsf@dod.no> <871utm5ree.fsf@dod.no> <87ty6i4c8u.fsf@dod.no> <87pqh649yk.fsf@dod.no> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1320564240 16899 80.91.229.12 (6 Nov 2011 07:24:00 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 6 Nov 2011 07:24:00 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M28820@lists.math.uh.edu Sun Nov 06 08:23:56 2011 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RMx5A-0005QC-9b for ding-account@gmane.org; Sun, 06 Nov 2011 08:23:56 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1RMx4a-000549-Uw; Sun, 06 Nov 2011 01:23:21 -0600 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1RMx4X-00053r-89 for ding@lists.math.uh.edu; Sun, 06 Nov 2011 01:23:17 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1RMx4K-0007nY-8n for ding@lists.math.uh.edu; Sun, 06 Nov 2011 01:23:14 -0600 Original-Received: from lo.gmane.org ([80.91.229.12]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1RMx4H-0005oU-El for ding@gnus.org; Sun, 06 Nov 2011 08:23:01 +0100 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RMx4G-0005AC-Nh for ding@gnus.org; Sun, 06 Nov 2011 08:23:00 +0100 Original-Received: from cm-84.208.231.161.getinternet.no ([84.208.231.161]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 06 Nov 2011 08:23:00 +0100 Original-Received: from sb by cm-84.208.231.161.getinternet.no with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 06 Nov 2011 08:23:00 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: ding@gnus.org Original-Lines: 39 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: cm-84.208.231.161.getinternet.no Mail-Copies-To: never User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:bJYzECircEB4cr0fkd+Zzr+YAUg= X-Spam-Score: -6.1 (------) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:80537 Archived-At: >>>>> Steinar Bang : [snip!] > The JSON in the log line ends abruptly. If I dump all of the JSON in > the log line to a file, I get a file of size 154991bytes, while the > POSTed file, as extracted from the wireshark dump, is 155005 bytes. > With 155k I probably don't hit any hard limits on couchdb doc size (I > haven't checkd what they are, though). > Could it be an error in the HTTP header...? > The header says > Content-length: 154991 > I guess that explains the cutoff, Here's also a difference from Teds setup: I'm running coucdb behind a reverse proxy apache. It could be that apache is stricter wrt content-length than couchdb...? (if so, that's a good thing when talking to the internet... expect that a client lying to you, is up to nothing good...). I tried one experiment, which was to copy the JSON file I extracted from the wireshark dump over to the server, and send it to couchdb, with the command: curl --data-binary @/tmp/lesync_sync.json --header "Content-Type: application/json" http://localhost:5984/sb This was successful. But a wireshark dump of the HTTP traffic on port 5984, showed that the content-length of the request was set to the correct 155005 bytes value. So this didn't prove anything other than that the lesync post from gnus have a wrong content-length... (Also, the wireshark dump showed that curl's POST request had an Expect: 100-Continue header, and that the client politely waited for a "100 Continue" response before sending the JSON in the request body to the server.)