Hello nzl,
> Subject: [surf[PATCH] Remove HTTP referer on navigation
Thank you, but I'm not sure what you want us to do with that.
Is this for mainline integration?
If so, I find it a bit too drastic, some websites don't work without
the correct referer (mostly with session).
This could be a
> Hi,
Hi Hiltjo,
> Some browsers have different "privacy" options like:
>
> 1. Strip the referer header entirely.
> 2. Only allow it for the same origin domains.
> 3. Allow "crossdomain" referer, but only set the domain part.
I think I would accept such a patch, again as long as it's coded as
Sorry, the previous one doesn't work, this one is tested. Still
some sites might *not* work without referer field in between of
HTTP redirections. I couldn't find a way to modify HTTP headers only
for those requests that're actually sent by users.
---
surf.c | 10 ++
1 file changed, 10
From 8ed3ce1f6ef48ee6e768dbf85c2c40d08a58b706 Mon Sep 17 00:00:00 2001
From: nzl
Date: Sun, 18 Nov 2018 18:01:52 +
Subject: [surf[PATCH] Remove HTTP referer on navigation
---
surf.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/surf.c b/surf.c
index d48fbc9..4175f06 100644
---
Hi all,
> Thank you, but I'm not sure what you want us to do with that.
>
> Is this for mainline integration?
That's my original thought.
> If so, I find it a bit too drastic, some websites don't work without
> the correct referer (mostly with session).
Yes, I've used it for a while now and
On Sun, Nov 18, 2018 at 07:47:00PM +0100, Quentin Rameau wrote:
> Hello nzl,
>
> > Subject: [surf[PATCH] Remove HTTP referer on navigation
>
> Thank you, but I'm not sure what you want us to do with that.
>
> Is this for mainline integration?
> If so, I find it a bit too drastic, some websites
