-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
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
证书为 GA *.c.docs.google.com 的大多数都不能用 ??? #7
Comments
就是不能用,只有三种证书可用 |
c.doc.google.com的话不知道在GoAgent加入GVS支持之后能不能用 |
@NKUCodingCat 貌似是可以的 C:\Windows\system32>curl -k -I https://173.194.4.146
HTTP/1.1 200 Tunnel established
HTTP/1.1 404 Not Found
Date: Tue, 09 Jun 2015 08:32:59 GMT
Content-Type: text/html; charset=UTF-8
Server: gvs 1.0
Content-Length: 1425
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
C:\Windows\system32>curl -k -I https://173.194.4.146 --ciphers ECDHE-RSA-AES128-SHA
HTTP/1.1 200 Tunnel established
HTTP/1.1 200 OK
Date: Tue, 09 Jun 2015 08:33:34 GMT
Expires: -1
Cache-Control: private, max-age=0
Content-Type: text/html; charset=ISO-8859-1
Set-Cookie: NID=68=HB2vPj9Xvg05y1c3ny6JY3HlK1GYEzH_Pgn4f2IkvYWBU3fpj61cUx2FKloBldgugaraFObnVuuKiqJS3QTtDBDj9ENbaeRE0hu1MhOsplvzsT_-8vB1cnUBPv5NugQD; expires=Wed, 09-Dec-2015 08:33:34 GMT; path=/; domain=.; HttpOnly
P3P: CP="This is not a P3P policy! See http://www.google.com/support/accounts/bin/answer.py?hl=en&answer=151657 for more info."
Server: gws
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
Alternate-Protocol: 443:quic,p=1
Transfer-Encoding: chunked
Accept-Ranges: none
Vary: Accept-Encoding |
嗯O.O……好像挺不错的样子我去升GoAgent |
@CNMan
|
@CNMan 测试代码 https://gist.github.com/NKUCodingCat/f70b9fd9d958ea5fad80 结果:
原因不明,反正我用Curl就不行╮(╯▽╰)╭ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
用旧版的搜到的IP 导入到 2.39 中证书显示都为 GA *.google.com ,,这些IP 全都能用 。。
但用 2.39 搜到的 ip 大多数是 GA *.c.docs.google.com ,, 这些 ip 标准测试和带宽测试都是正常的,但放到 goagent 中就死活不能用?? 请问有什么办法解决吗?? 怎样才能使用证书为 GA *.c.docs.google.com 的 ip ???
The text was updated successfully, but these errors were encountered: