From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] 201
Date: Wed, 18 Feb 2015 06:26:08 -0800 [thread overview]
Message-ID: <87d257l2in.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20150117213549.eklhad@comcast.net> (Karl Dahlke's message of "Tue, 17 Feb 2015 21:35:49 -0500")
Karl Dahlke <eklhad@comcast.net> writes:
> Should I be treating this like 301 302 303 etc, looking for
> location=
> in the http headers, and jumping to that if present?
It isn't really clear to me, either. I mean, a 2xx response code
indicates success, and a 3xx code indicates a redirect.
I don't think we're supposed to redirect on a 201.
I'm even more convinced after seeing this discussion on stackoverflow:
http://stackoverflow.com/questions/4584728/redirecting-with-a-201-created
-- Chris
prev parent reply other threads:[~2015-02-18 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 2:35 Karl Dahlke
2015-02-18 14:26 ` Chris Brannon [this message]
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=87d257l2in.fsf@mushroom.localdomain \
--to=chris@the-brannons.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).