We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
user_spac.json
{ "Host" : ["accounts.youtube.com", "twitter.com", "login.yahoo.com"], "Proxy":["socks://127.0.0.1:3439", "SSH"] },
log
2013/03/03 10:35:58 gae.go:526: Session[1]Request CONNECT https://twitter.com:443
显示twitter.com还是连接到gae,而不是走自定义代理.
如果走自定义代理的话,应该就不需要导入证书了吧? 我拿https://login.yahoo.com/测试了下,貌似的确可以.
2013/03/03 10:45:45 ssh.go:105: Session[6]Request CONNECT https://login.yahoo.com:443
不晓得twitter.com规则是命中cloud_spac.json的规则,还是snova-gfwlist.pac里的规则,这个命中规则希望有熟悉的朋友能够讲解下
The text was updated successfully, but these errors were encountered:
规则优先级是 user_pre_spac.json cloud_spac.json, user_spac.json, twitter.com规则已经在cloud_spac.json, 你需要写到user_pre_spac.json中(user_pre_spac.json需要自己创建)
Sorry, something went wrong.
谢谢 写到user_pre_spac.json就解决了此问题
No branches or pull requests
user_spac.json
log
显示twitter.com还是连接到gae,而不是走自定义代理.
如果走自定义代理的话,应该就不需要导入证书了吧?
我拿https://login.yahoo.com/测试了下,貌似的确可以.
不晓得twitter.com规则是命中cloud_spac.json的规则,还是snova-gfwlist.pac里的规则,这个命中规则希望有熟悉的朋友能够讲解下
The text was updated successfully, but these errors were encountered: