From: Adam Thompson <arthompson1990@gmail.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] edbrowse erroneously prints a warning on receiving a 201 status code
Date: Tue, 17 Feb 2015 09:49:23 +0000 [thread overview]
Message-ID: <20150217094923.GA31398@toaster.adamthompson.me.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
Hi,
Minor cosmetic (I guess) bug. When using a system at work I see the following
for a particular web request (triggering a job with the Jenkins CI system in
case you're interested):
warning: http error 201, CreatedAccepted
Whereas it's useful to see the response code (Jenkins returns no response body)
it's also wrong to print a warning since the response code actually indicates success.
I'm wondering in these cases whether it'd be useful to have a command to
display the response code when you get a non-error response code but a 0-length
response (though I think keeping the current behavior with 404 and friends is a good thing).
Cheers,
Adam.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
reply other threads:[~2015-02-17 9:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150217094923.GA31398@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=edbrowse-dev@lists.the-brannons.com \
/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 NNTP newsgroup(s).