Why was IRUnfilter created?
The technical specs on how to easily bypass Iran's filtering, on any circumstances, without requiring a VPN or Proxy server, is thoroughly explained in my blog in Persian. The content filtering inspects HTTP requests and seeks Host header for filtered keywords, so this plugin effectively removes the host header.
Removing any required header (which is only "host" header) would make an HTTPS request fail, so the add-on automatically stops the procedure for HTTPS requests. After all, HTTPS requests could not be inspected and are filtered on IP basis.
Since some websites are on shared hostings, removing Host header would confuse their server on which website is required on the host (they all share the same IP), so in such cases, a 403 Bad Request error is returned by the web server.
These sorts of limitations, as well as HTTPS IP-based filtering, can also be dealt with by a HTTP Proxy, which the add-on gets the configuration on its options page, and automatically sets when enabled. After this, any webpage is browsable without encountering any filtering.
What's next for IRUnfilter
Means on how to bypass limitations which require a HTTP Proxy at the moment are under research. Some encoding changes might appear in the next releases that mitigate the need for a HTTP proxy on multi-site hosts.
Also add-on will start to cache filtered pages (according to their response) and don't do what it does for sites that are not filtered.
About the Developer
|User since||March 12, 2012|
|Number of add-ons developed||1 add-on|
|Average rating of developer's add-ons||Rated 2 out of 5 stars|
Who is AbiusX?
www.abiusx.com/cv for my resume