unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: peder@klingenberg.no (Peder O. Klingenberg)
Cc: 27012@debbugs.gnu.org
Subject: bug#27012: 26.0.50; eww does not generate Referer headers
Date: Thu, 13 Jul 2017 09:16:42 +0200	[thread overview]
Message-ID: <mvmo9so7qn9.fsf@suse.de> (raw)
In-Reply-To: <m17ezdp8a3.fsf@klingenberg.no> (Peder O. Klingenberg's message of "Thu, 13 Jul 2017 01:03:48 +0200")

On Jul 13 2017, peder@klingenberg.no (Peder O. Klingenberg) wrote:

> With the basic mechanism for sending the Referer header then working, I
> looked at limiting the distribution of it.  url-privacy-level already
> existed, and had a basic on-off-knob for referrers, or "lastloc", as it's
> called in that variable.  I left that alone, but added an additional
> user option - url-lastloc-privacy, with possible values "none",

Perhaps url-lastloc-privacy-level, to rhyme with url-privacy-level.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."





  reply	other threads:[~2017-07-13  7:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-21 21:41 bug#27012: 26.0.50; eww does not generate Referer headers Lars Ingebrigtsen
2017-05-22 12:18 ` Richard Stallman
2017-05-22 12:28   ` Lars Ingebrigtsen
2017-05-22 16:37     ` Glenn Morris
2017-05-22 16:53       ` Lars Ingebrigtsen
2017-07-12 23:03         ` Peder O. Klingenberg
2017-07-13  7:16           ` Andreas Schwab [this message]
2017-07-13 14:02             ` Peder O. Klingenberg
2018-04-13 13:09               ` Lars Ingebrigtsen
2018-04-13 13:33                 ` Peder O. Klingenberg
2018-04-13 13:39                   ` Lars Ingebrigtsen
2017-05-23  0:54     ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=mvmo9so7qn9.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=27012@debbugs.gnu.org \
    --cc=peder@klingenberg.no \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).