From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.help Subject: Re: url-retrieve-synchronously results differ from curl Date: Tue, 20 Jan 2015 13:35:29 -0200 Message-ID: References: <87y4oxewcc.fsf@yahoo.fr> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1421768219 31016 80.91.229.3 (20 Jan 2015 15:36:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 20 Jan 2015 15:36:59 +0000 (UTC) Cc: Sean Allred , help-gnu-emacs To: Nicolas Richard Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Jan 20 16:36:59 2015 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YDarR-0004l8-0N for geh-help-gnu-emacs@m.gmane.org; Tue, 20 Jan 2015 16:36:57 +0100 Original-Received: from localhost ([::1]:44034 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YDarQ-0003wn-3l for geh-help-gnu-emacs@m.gmane.org; Tue, 20 Jan 2015 10:36:56 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37557) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YDaq5-0002jl-Tf for help-gnu-emacs@gnu.org; Tue, 20 Jan 2015 10:35:40 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YDaq2-0006An-4a for help-gnu-emacs@gnu.org; Tue, 20 Jan 2015 10:35:33 -0500 Original-Received: from mail-oi0-x22e.google.com ([2607:f8b0:4003:c06::22e]:49688) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YDaq2-0006AI-09 for help-gnu-emacs@gnu.org; Tue, 20 Jan 2015 10:35:30 -0500 Original-Received: by mail-oi0-f46.google.com with SMTP id a141so6910146oig.5 for ; Tue, 20 Jan 2015 07:35:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=YwWXyJtSXMr3xFiiZ3/a1tbh9ajZRT0MQVQZmoVudaQ=; b=vsziUrgpbVacGXAjkEEwl4mjB01U0ia4/Pjn7RTj6IJ7/12bJaT339nrh8AVS9GWGn 4qygKjICnTlV8+YvXW9Hf7F7lp97wr/QpbqTATbg+cnjcezmUnP2dMoOwNxd7HhTiPg/ xzu+RfM3lcVgTPYEF0FrS9vlXE4X4EhMat7Xrq/KcY+OAdYuWmPW5Q8vj+tsYiV5pKFy iBXpLEN2Q2keXGphl5Igzxhi/BYos8eHTmzKcMjXYpVgqsgRCUIdRz6SZK8+9L4pxM/e /8XFC2NzU/p1RUCA40wgwoDqn40vMKLwl+DVmKHuakRRsfzhHrTsgYCE9HEyyE1GDegZ 2hNQ== X-Received: by 10.202.50.136 with SMTP id y130mr20720997oiy.91.1421768129385; Tue, 20 Jan 2015 07:35:29 -0800 (PST) Original-Received: by 10.76.125.1 with HTTP; Tue, 20 Jan 2015 07:35:29 -0800 (PST) In-Reply-To: <87y4oxewcc.fsf@yahoo.fr> X-Google-Sender-Auth: Ea-xIEBbT6QK2pKIuT4fGwPq0fY X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4003:c06::22e X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:102171 Archived-At: >> It's possible this is just a bug in the API we're posting to, but it's >> more likely we just haven't built this request correctly in >> url-retrieve-synchronously. This would explain why it's being handled >> differently from the request we make with curl. > > (I'm going a bit off topic here, sorry about that.) > > Did you inspect the actual request being sent via e.g. wireshark (this > is GPL software) ? Perhaps you can spot a difference and get at least a > starting point. > > If you never used wireshark, here's how I would do it : > > 1. type something in the filter box (near the top) like: > (ip.src==208.118.235.148 or ip.dst == 208.118.235.148) and http > That would only show HTTP traffic from/to gnu.org. > 2. select a capture interface (e.g. eth0) and hit start > 3. send the requests > 4. hit "Stop" and inspect what you've got. Thanks for the suggestion. I've managed to follow the steps above, but I can't say I fully understand the results. A single call to `url-retrieve-synchronously' yields 11 entries meeting the ip.dst filter (most TCP and a few TLS). I tried looking through these entires to figure out what data/headers were being sent, but had no success.