From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] missing https referer
Date: Thu, 01 May 2014 06:21:11 -0400 [thread overview]
Message-ID: <20140401062111.eklhad@comcast.net> (raw)
Chuck,
This was an easy fix.
For some reason send referer was off by default.
So I just set it to on.
This is what other browsers do, on by default,
so I think we're ok here.
It can be toggled with the sr command,
and I guess other browsers also let you turn it on and off,
so I'll keep that feature around.
If you start with an empty buffer, then jump to a website,
there is no referer, which I think is corect.
If you refresh a web page, the referer is the page you are on,
which is probably not correct, (bug?),
it should probably be the page that you came from before the refresh.
Not sure about that one.
Karl Dahlke
next reply other threads:[~2014-05-01 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 10:21 Karl Dahlke [this message]
2014-05-01 10:50 ` Charles Hallenbeck
-- strict thread matches above, loose matches on Subject: below --
2014-05-01 9:41 Charles Hallenbeck
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=20140401062111.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).