From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: Sean Allred <code@seanallred.com>,
help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: url-retrieve-synchronously results differ from curl
Date: Tue, 20 Jan 2015 08:37:39 +0100 [thread overview]
Message-ID: <87y4oxewcc.fsf@yahoo.fr> (raw)
In-Reply-To: <CAAdUY-LUCEf8ftozE4S=LgKb6S5T3Weg7Bmt6NpR+ioVbRkMWQ@mail.gmail.com> (Artur Malabarba's message of "Tue, 20 Jan 2015 00:28:46 -0200")
Artur Malabarba <bruce.connor.am@gmail.com> writes:
> 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.
HTH,
--
Nicolas
next prev parent reply other threads:[~2015-01-20 7:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 2:28 url-retrieve-synchronously results differ from curl Artur Malabarba
2015-01-20 7:37 ` Nicolas Richard [this message]
2015-01-20 15:35 ` Artur Malabarba
2015-01-21 7:13 ` Nicolas Richard
2015-01-21 13:14 ` Artur Malabarba
2015-01-21 13:42 ` Nicolas Richard
2015-01-21 14:27 ` Sean Allred
2015-01-21 16:29 ` Thien-Thi Nguyen
2015-01-22 1:14 ` Artur Malabarba
2015-01-22 2:41 ` Artur Malabarba
2015-01-22 9:00 ` Thien-Thi Nguyen
2015-01-21 8:01 ` Thien-Thi Nguyen
2015-01-21 14:14 ` Artur Malabarba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y4oxewcc.fsf@yahoo.fr \
--to=theonewiththeevillook@yahoo.fr \
--cc=bruce.connor.am@gmail.com \
--cc=code@seanallred.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).