google-code-export / wallproxy-plugins

Automatically exported from code.google.com/p/wallproxy-plugins
0 stars 0 forks source link

作PHP代理时又遭遇到自动切换HTTPS导致SSL错误 #129

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
forold = [{
    'url': 'http://xxxx/fetch.php',
    'key': '',
    'crypto':'XOR--32',
    'proxy': '',
},{
    'url': 'http://yyyy/fetch.php',
    'key': '',
    'crypto':'XOR--32',
    'proxy': '',
}]

    if dnsDomainIs(url.hostname, 'xxxxx.com'): 
        return forold
    if dnsDomainIs(url.hostname, 'zzzzz.de'): 
        return forold

Original issue reported on code.google.com by kagami0...@hotmail.com on 10 Jun 2011 at 1:36

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
除了降回1.04的用户端 
1.06的服务端发现可以用外.只要是1.05以上的版本都会挂掉.本�
��把自己的拷贝给他结果一急没注意把自己的也覆盖了.这下��
�剧了....

该怎么处理才能正常使用啊...现在即使用1.04的设置重新设然�
��覆盖1.05的文件都没用

Original comment by kagami0...@hotmail.com on 10 Jun 2011 at 2:31

GoogleCodeExporter commented 9 years ago
问题还是跟上次一样,不过这次是不管怎么改设置都会直接弹�
��用https代替http然后导致各种代理错误.....最后只好降用户端�
��来了.

Original comment by kagami0...@hotmail.com on 10 Jun 2011 at 2:47

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
1、syangrila.com这个域名是否是走PHP的?是的话,说明你所在的
环境无法正常访问你的PHP服务端
2、在自动改用https时存在范围扩大的缺陷,如果你的PHP空间��
�支持https访问的话,就会出现这个问题,但即使不扩大可能��
�无法正常使用
3、不久后会出新版本

Original comment by dtma...@163.com on 10 Jun 2011 at 4:05

GoogleCodeExporter commented 9 years ago
@ 7 

发现是无法访问php服务器(其中一个被GFW给X了)然后导致无限��
�动切换.加入自动代理信息后完毕,发现速度更快了(好怪异)

Original comment by kagami0...@hotmail.com on 10 Jun 2011 at 4:12

GoogleCodeExporter commented 9 years ago
现在GFW的魔掌快遍布世界了.以后要走代理都难了...前段时间�
��买没多久的VPN也挂了.唉

Original comment by kagami0...@hotmail.com on 10 Jun 2011 at 4:15

GoogleCodeExporter commented 9 years ago

Original comment by dtma...@163.com on 11 Jun 2011 at 4:43