Handle "Redirect" blocking policy

[madeye]

Some networks, e.g. a typical company intranet, will block connections by applying "redirect" policy. They often redirect blocked connections to a warning page or a login page. It means there could exist no reset or timeout for blocked sites. In some situations, we can even get HTTP 200 code when trying to reach a non-existent site.

Furthermore, some DNS pollution/injection techniques enable ISPs to do almost the same things for advisement. An example is that China telecom redirects users to 114 search when they are trying to visit a non-existent or blocked site.

[cyfdecyf]

I think it would be difficult to detect whether a site is actually blocked in that case. Do you have any suggestions?

The solution currently available in COW is to manually specify blocked sites in ~/.cow/blocked, so theoe sites would always use the parent socks proxy.

Best regards,
Chen Yufei

On 2012年11月29日Thursday at 下午3:06, Max Lv wrote:

Some networks, e.g. a typical company intranet, will block connections by applying "redirect" policy. They often redirect blocked connections to a warning page or a login page. It means there could exist no reset or timeout for blocked sites. In some situations, we can even get HTTP 200 code when trying to reach a non-existent site.
Furthermore, some DNS pollution/injection techniques enable ISPs to do almost the same things for advisement. An example is that China telecom redirects users to 114 search when they are trying to visit a non-existent or blocked site.

—
Reply to this email directly or view it on GitHub (#8).