From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (75-164-214-250.ptld.qwest.net [75.164.214.250]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id EB9F7794E1 for ; Wed, 18 Feb 2015 06:26:31 -0800 (PST) From: Chris Brannon To: Edbrowse-dev@lists.the-brannons.com References: <20150117213549.eklhad@comcast.net> Date: Wed, 18 Feb 2015 06:26:08 -0800 In-Reply-To: <20150117213549.eklhad@comcast.net> (Karl Dahlke's message of "Tue, 17 Feb 2015 21:35:49 -0500") Message-ID: <87d257l2in.fsf@mushroom.localdomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] 201 X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2015 14:26:32 -0000 Karl Dahlke 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