Opened 2 years ago
Closed 2 years ago
#2084 closed enhancement (wontfix)
Allow filtering of javascript, plugins and redirects for the http client tunnel
| Reported by: | Reportage | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | undecided |
| Component: | apps/i2ptunnel | Version: | 0.9.32 |
| Keywords: | http client, filtering, security | Cc: | |
| Parent Tickets: | Sensitive: | no |
Description
The HTTP client tunnel already allows filtering of certains elements:
- User Agent
- Accept headers
- Referrer
To enhance security, permit optional filtering of:
- javascript (linked and inline)
- Browser plugins
- Redirects (meta and 30* server redirects) with redirect url displayed instead
Subtickets
Note: See
TracTickets for help on using
tickets.
I appreciate the wish. However, our proxy is a typical HTTP proxy that processes headers but not content, and we can't even do that if it's HTTPS. Parsing and modifying content is far beyond what's sensible or appropriate. It's best done in the user agent (i.e. browser) or its plugins (e.g. noscript) where there's a parsed DOM.
In response, you may say we should ship something similar to Tor Browser, but that's not within the current team's capabilities to develop and package that, and won't ever be.