Open GoogleCodeExporter opened 9 years ago
不知道支持不支持中文,我就有个小小的问题。在app.yaml中是
不是secure:optional有错误?
非常感谢
Original comment by opens...@gmail.com
on 19 Feb 2009 at 9:07
Openstar:
There are users who want to use Mirrorrr in a way that is not secure. That is
why it
is optional.
You must click the "secure" button to go secure, or access
https://mirrorrr.appspot.com.
Crude translation:
有用户谁想要使用Mirrorrr的方式并不安全。这就是为什么它是
可选的。
您必须单击“安全”按钮,转到安全,或访问网址为: https
: / / mirrorrr.appspot.com 。
Original comment by bslatkin
on 19 Feb 2009 at 6:42
多谢楼主,我现在的问题是每次都会有下面的问题出现
E:\Google\google_appengine>appcfg.py update inter18099
Error parsing yaml file:
Unexpected attribute 'secure' for object of type < class
'google.appengine.api.ap
pinfo.URLMap' >.
in "inter18099\app.yaml", line 15, column 11
这个问题怎么解决?是哪里的错误?多谢指教
Original comment by opens...@gmail.com
on 25 Feb 2009 at 8:49
[deleted comment]
you must update your GoogleAppSDK to 1.1.5 or better.
Original comment by bygree...@gmail.com
on 17 Mar 2009 at 2:23
可不可以支持url编码(如rot13),因为有url过滤?
可不可以支持cookies?
这样就完善了
Original comment by xixinxing
on 31 May 2009 at 4:25
出现secure:optional错误的
使用google官方的SDK
不要使用第三方上传工具
那个已经过时了
Original comment by qyz...@gmail.com
on 7 Oct 2009 at 11:58
I also believe url encryption is necessary. As u know, GFW blockes sites by url
too.
rot13 is a simple but effective way to encrypt url.
Original comment by forest...@gmail.com
on 26 Dec 2009 at 9:24
new features about mirrorrr published here :
http://code.google.com/p/mirrorrr-plus
1.url encryption : base64 encoded
2.form/POST : some site is ok. ( i'll keep work on it )
3.chinese encode to &#XXXX;
demo site is here: http://mirrorrr-plus.appspot.com/
基于mirrorrr的增强,发布在这里:
http://code.google.com/p/mirrorrr-plus
1.url编码: 基于base64编码
2.form/POST提交: 部分网站已经可以.
(部分网站不行,我会继续修正 )
3.中文编码成这种格式:&#XXXX;
演示网站: http://mirrorrr-plus.appspot.com/
Original comment by LJX...@gmail.com
on 29 Sep 2010 at 6:57
This project is really incredible!! Well done to the developer. Could you
enable login process also?
Original comment by ihsana...@gmail.com
on 20 Jan 2011 at 2:48
Original issue reported on code.google.com by
myzj12...@gmail.com
on 16 Jan 2009 at 12:20