From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 24A9277C83 for ; Sun, 27 Dec 2015 05:38:21 -0800 (PST) Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by resqmta-ch2-03v.sys.comcast.net with comcast id yde91r0042TL4Rh01degmX; Sun, 27 Dec 2015 13:38:40 +0000 Received: from eklhad ([IPv6:2601:405:4001:e487:21e:4fff:fec2:a0f1]) by resomta-ch2-17v.sys.comcast.net with comcast id ydef1r00E2MDcd701defCk; Sun, 27 Dec 2015 13:38:40 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20151122181357.eklhad@comcast.net> User-Agent: edbrowse/3.6.0+ Date: Sun, 27 Dec 2015 08:38:39 -0500 Message-ID: <20151127083839.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1451223520; bh=LWryLU7Gz/mbMnmmenDhNgYpqSDW3t4MT2WWlwV/yRA=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=oWLeZj0inDbjICdQU4MK5Odujtg7Yyl9JKZHah+OnB03lG1Kw+aRdLQbmMfCGEIoD fnNIc68yFaoiKJY9YQbaB0jPV6zBmeBJUQsVzH9PmofZq6cJeNjDxe3wjXwWiJpqSl 9ZQmVOQ0UetkR1QgYqS1ecwd5lZcp12jxqELLiKmgpdFs0cjtvi3KZSiIFVuXKB3vi 1FIW97Obu2olHKrr19EIdDd9ZLErItNYyjz3v9boprnqL0EkXUZ2WU/TLisa0tIePw pHroJyjekZbJArqEyrSngdaPmKHT2Cj3TmtlRt2nZRkxZDSBVPkKgKvN68pILipU8Q u1Fd+U42rECHQ== Subject: [Edbrowse-dev] response headers and body? X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Dec 2015 13:38:21 -0000 > Is there a way to return the entire 'raw' response with > headers on the beginning? No but there could be easily, or better, return both the headers and the body. Headers are captured in the string http_headers in http.c, we just need to return it to the caller. I'll look at this later; after Chris finishes his work in http.c. I don't want to collide. Let's just say we can easily do this. > it could be wrapped in: if (xhr) sure, and probably in the else clause simulate not being able to connect to the website and let js march on and do whatever it would have done in that case. I mean, sometimes you can't get to a site, especially a different one from the site you just fetched. Google analytics or some such. Karl Dahlke