J2ME额外烦人的HTTP权限提示
有些手机仅在第一次建立连接时提示用户获得许可。 其他的则每当 MIDlet 尝试建立 HTTP 连接时都会弹出权限提示！ 如果我们想抑制提示，有哪些选项？
我们可以仅使用一个 CA（证书颁发机构）对 JAR 进行签名并使其在所有设备上运行吗？ 我们是否必须为每个版本的签名付费？
是否可以选择创建我们自己的 CA 证书并告诉我们的客户将其安装在设备上？
另外，普通的套接字连接似乎不会受到这样的影响。 J2ME 是否有基于 TCP 的免费 HTTP 实现？
Some phones only prompt the user for permission the first time a connection is made. Others pop up the permission prompt whenever the MIDlet attempts to make a HTTP connection! What are the options if we want to suppress the prompt?
Can we sign the JAR using only one CA (Certificate Authority) and have it work on all devices? Do we have to pay for a signature on every release?
Is it an option to create our own CA certificate and tell our customers to install it on there device?
Alternatively, it seems that plain socket connections do not suffer so. Is there a free implementation of HTTP on top of TCP for J2ME?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
有些手机允许您手动更改设置以每次会话设置一次。 或者尝试将
MIDlet-Permissions: javax.microedition.io.connector.http添加到 jad 文件中。
是的，如果版本是使用大多数设备上可用的根证书进行签名的，例如 Verisign 3 类证书
作为安全措施，设备不允许您安装自己的证书，即使它是从 CA 获取的。
普通套接字连接可能会增加客户端数据处理的开销。 另外还涉及到一些安全问题。
Some phones allow you to change the setting manually to set once per session. Or try adding
MIDlet-Permissions: javax.microedition.io.connector.httpto the jad file.
Yes, if the build is signed with the root certificate that is available on most devices, Verisign Class 3 certificate, for example
As a security measure, devices don't allow you to install your own certificates, even if it is obtained from a CA.
Plain socket connections may add overhead in processing of the data in the client side. Also some security issues are also involved.
签署 JAR 并不能保证在所有手机和所有网络上抑制这些提示。 它可能对某些人有效。 AFAIK 你通常需要为每个构建签名； 因此，如果您在许多手机上使用相同的版本，则只需签名一次。
您可以通过套接字编写自己的 HTTP 实现，但请注意 Socket 实现不允许访问端口 80 和 8080（同样，AFAIK）。
当遇到多个 HTTP 提示时，最好的选择是将用户引导至其手机菜单中的 MIDlet 权限设置； 这应该改为“询问一次”。
哈特哈，
放克布罗
Signing the JAR is not guaranteed to suppress these prompts on all handsets and all networks. It may work on some. AFAIK you usually need to sign per build; so if you use the same build on many handsets, you need to sign only once.
You could write your own implementation of HTTP over sockets, but beware that Socket implementations do not allow access to ports 80 and 8080 (again AFAIK).
Your best option when experiencing multiple prompts for HTTP is to direct the user to the MIDlet permissions setting in their handset menu; this should be changed to "ask once".
HTH,
funkybro
Java Verifieds UTI 根证书并不适用于所有手机/网络组合，对于可信第三方中的其他域（例如 Verisign 和 Thawte）也是如此（对于这些机构，特别是摩托罗拉设备）
公平地说，UTI 证书是可能是为您提供跨手机覆盖范围最广的选择之一
Java Verifieds UTI root certificate is not on all handsets/network combinations, the same is true for other domains in the trusted third party such as Verisign and Thawte (for these bodies in particular Motorola devices)
It is fair to say that the UTI certificate is probably the one to choose to give you the most coverage across handsets
要抑制 HTTP 连接提示，签署应用程序是唯一的选择。 另一种方法是在预售手机上进行预加载，但即使是手机制造商也需要签名的 jad/jar。
使一组 jad/jar 在不同设备上工作并不取决于签名，而是取决于您如何设计应用程序。 如果您能解决这个问题，那么是的，您可以让一个签名的 jad/jar 在多个设备上工作。
我不知道如何创建我们自己的证书并要求客户安装它们。 我认为它不起作用，因为我认为这是不可能的。
HTTP over TCP 是一个相当简单的实现，只要您知道自己在做什么，但我不知道有任何免费的实现。
To suppress the HTTP connection prompt, signing an app is the only option. Another would be to get preload on a pre-market phone, but even the handset manufacturers require signed jad/jars.
Making a set of jad/jar work on different devices is not dependent on signing but how you design an app. If you can address this then yes, you can have one signed jad/jar work on multiple devices.
I do not know about creating our own certs and asking customers to install them. I dont think it works as I dont think it is possible.
HTTP over TCP is a fairly easy implementation, provided you know what you are doing, but I dont know of any free implementations of it.
获得 Java 验证后，您会发现在所有网络和手机上 - 用户每次启动应用程序以授权连接时只会收到一次提示。
Get it Java Verified and you will find that on all networks and phones - the user will get prompted only once each time they start the app to authorise a connection.