3 Apr
2016
3 Apr
'16
4:16 p.m.
On Sat, 2 Apr 2016 18:14:26 -0400 Ian Goldberg <iang@cs.uwaterloo.ca> wrote:
On Sat, Apr 02, 2016 at 07:19:30PM +0000, Yawning Angel wrote:
It's not a request header set by the browser. archive.is is acting like a HTTP proxy and explicitly setting X-F-F.
I wonder what would happen if the browser *also* set X-F-F...?
Unfortunately, it appears that archive.is tramples over X-F-F if it is already set. Maybe others will have better luck engaging with the operator(s) of archive.is than I have. Regards, -- Yawning Angel