Opened 8 years ago

Closed 22 months ago

#785 closed defect (fixed)

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: 0.9.41
Component: apps/i2ptunnel Version: 0.9.3
Keywords: header Cc:
Parent Tickets: Sensitive: no


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.


Change History (3)

comment:2 Changed 8 years ago by str4d

Milestone: 0.9.4
Summary: Forbid I2PTunnel to send "X-Accept-Encoding:" header and filter out "Accept-Encoding:" headerHTTP 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.

comment:3 Changed 22 months ago by idk

Milestone: 0.9.41
Resolution: fixed
Sensitive: unset
Status: newclosed
Type: enhancementdefect

I have tested this and looked at the corresponding code, it appears to have been fixed for quite a long time.

Note: See TracTickets for help on using tickets.