Support new 'Forwarded' standard (RFC7239) about trafficserver HOT 9 CLOSED

We should make the old behavior optional to enable as well, there's a significant number of backends (origins) that do not support RFC7239 yet but need the old semantics.

from trafficserver.

I thought the old behavior was already optional.

{RECT_CONFIG, "proxy.config.http.insert_squid_x_forwarded_for", RECD_INT, "1", RECU_DYNAMIC, RR_NULL, RECC_NULL, NULL, RECA_NULL}

from trafficserver.

Right, but your comments say "replaces". I think we should keep both, indefinitely.

from trafficserver.

Fair enough, description fixed.

from trafficserver.

I have some one here at Y! who will be working on this.

from trafficserver.

To records.config I'm thinking to add:

CONFIG proxy.config.http.insert_forwarded STRING {value}

{value} would either be 'none' (the default) or list of options, separated by '|' (pipe).

options:

for
by={by-value}
proto
host
connection

These would enable variables in the header. "connection" is a non-standard variable, which will contain the most verbose protocol specifier from the "Via:" header.

{by-value} can be "ip", "unknown", "servername" or "uuid". The UUID would have a prepended _ (underscore) to make it a legitimate obfuscated identifier per RFC 7239.

from trafficserver.

I'd like to add to "connection" the ability to specific some levels of detail, e.g.
connection=full
connection=std
connection=compact
with the same meaning as for the VIA header.

from trafficserver.

It's already in there and ready to be savaged.

from trafficserver.

I believe this has been fully completed. Please reopen if need be.

from trafficserver.