Opened 7 years ago

Last modified 6 years ago

#785 new enhancement

HTTP client tunnel: Don't send "X-Accept-Encoding:" or "Accept-Encoding:" headers when connecting via outproxy

Reported by: serrgio Owned by:
Priority: minor Milestone:
Component: apps/i2ptunnel Version: 0.9.3
Keywords: header Cc:
Parent Tickets:

Description

I suggest disable sending
"X-Accept-Encoding: x-i2p-gzip;q=1.0, identity;q=0.5, deflate;q=0, gzip;q=0, *;q=0" header by HTTP client tunnel and filter out
"Accept-Encoding:" header at HTTP proxy. Such headers may reveal I2P when network used in couple with proxy, if proxy operator does not set own software to remove outgoing headers.

Subtickets (add)

Change History (2)

comment:2 Changed 6 years ago by str4d

  • Milestone 0.9.4 deleted
  • Summary changed from Forbid I2PTunnel to send "X-Accept-Encoding:" header and filter out "Accept-Encoding:" header to HTTP client tunnel: Don't send "X-Accept-Encoding:" or "Accept-Encoding:" headers when connecting via outproxy

Reading the above topic, the OP's proposal is unworkable - there is no point disabling gzip compression for connections within I2P, and we have no control over what the outproxy providers choose to filter.

An alternative workable proposal is that the (X-)Accept-Encoding: headers are not added when the destination is outside I2P and the client tunnel is going to route the connection to an outproxy.

Note: See TracTickets for help on using tickets.