From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] response headers and body?
Date: Sun, 27 Dec 2015 08:38:39 -0500 [thread overview]
Message-ID: <20151127083839.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1512270053470.12373@carhart.net>
> 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
next prev parent reply other threads:[~2015-12-27 13:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 23:13 [Edbrowse-dev] Rebundle Karl Dahlke
2015-12-23 23:17 ` Kevin Carhart
2015-12-24 0:01 ` Kevin Carhart
2015-12-24 0:04 ` Kevin Carhart
2015-12-24 0:17 ` Karl Dahlke
2015-12-24 0:46 ` Kevin Carhart
2015-12-25 15:10 ` Karl Dahlke
2015-12-26 8:44 ` [Edbrowse-dev] Rebundle / One program # processes Kevin Carhart
2015-12-26 15:56 ` Karl Dahlke
2015-12-27 7:54 ` Adam Thompson
2015-12-27 9:18 ` [Edbrowse-dev] response headers and body? Kevin Carhart
2015-12-27 13:38 ` Karl Dahlke [this message]
2015-12-27 21:03 ` Kevin Carhart
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=20151127083839.eklhad@comcast.net \
--to=eklhad@comcast.net \
--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).