From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (unknown [IPv6:2602:47:2243:ea00:12bf:48ff:fe7c:5584]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id 2F8E877DA9 for ; Tue, 22 Apr 2014 10:02:35 -0700 (PDT) From: Chris Brannon To: Edbrowse-dev@lists.the-brannons.com References: <20140322124550.eklhad@comcast.net> Date: Tue, 22 Apr 2014 10:02:14 -0700 In-Reply-To: <20140322124550.eklhad@comcast.net> (Karl Dahlke's message of "Tue, 22 Apr 2014 12:45:50 +0000") Message-ID: <87mwfduwkp.fsf@mushroom.PK5001Z> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] Refresh http header X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.17 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2014 17:02:35 -0000 Karl Dahlke writes: > Is this http codes 301 and 302? No. This is an HTTP header created by Netscape years ago, and it has never been included in the standards! It serves the same place as a tag in HTML. These two things are equivalent: Refresh: 30;url=http://the-brannons.com/ in HTTP headers, and in HTML. We could extract the header in libcurl and then pass it along when parsing the HTML, I suppose. Here's the question. Which takes precedence: the Refresh header or the meta tag? -- Chris