W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2011

Re: I-D draft-petersson-forwarded-for-00.txt

From: Andreas Petersson <andreas@sbin.se>
Date: Tue, 19 Apr 2011 11:09:17 +0200
To: "Poul-Henning Kamp" <phk@phk.freebsd.dk>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Cc: Mark Nottingham <mnot@mnot.net>, Willy Tarreau <w@1wt.eu>, "Thomson, Martin" <Martin.Thomson@commscope.com>, Karl Dubost <karld@opera.com>
Message-ID: <20110419110917.55c89768@hetzer>
On Tue, 19 Apr 2011 07:53:33 +0000
"Poul-Henning Kamp" <phk@phk.freebsd.dk> wrote:

> In message <8F735513-6A44-4043-B7DA-EAE1E2FD1A0D@mnot.net>, Mark Nottingham wri
> tes:
> >> Forwarded: for=, for=;by=
> >> Forwarded: for=;by=;proto=https
> This format needs a strict definition to be unambigious.
> For instance, if the first proxy adds only "for" and the next adds
> only "by", there is no way to tell if one or two proxies were
> involved.

One proxy should add one element, which is a list of key=values
separated by semicolon.

Two proxies:
Forwarded: for=, by=

One proxy:
Forwarded: for=; by=

Or do I miss something?

> I still think it is a better idea that each proxy adds exactly one
> element, and that the single element contains whatever information
> the proxy is willing to disclose.

Can you give an example of how such an element would look like?
Only sending the IP-address of the client you are forwarding for would
maybe be the cleanest, but there seems to be a need for disclosing
other information too when proxying. That information would need to be
connected to the forwarded-for somehow. 


would be ambiguous.

I am afraid that one will sooner or later see the need for
standardizing also X-Fowarded-(By|Proto|Host ...) and doing that and
keeping the format of Forwarded-For would be hard. 
I don't think it'd be a good situation if we had yet another way of
disclosing such information, therefore maybe it's better to support all
of them here? 

/Andreas Petersson
Received on Tuesday, 19 April 2011 09:10:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:13:51 UTC