IBM Worklight 5.0.6.1-通过代理服务器推送通知 [英] IBM Worklight 5.0.6.1 - Push Notification through Proxy Server

查看:62
本文介绍了IBM Worklight 5.0.6.1-通过代理服务器推送通知的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我想使用代理服务器进行推送通知.在worklight.properties中,如何为APNS指定用户名和密码?

I would like to use a proxy server for push notification. In worklight.properties, how to specify username and password for APNS?

#   Push GCM proxy settings
#push.gcm.proxy.enabled=false
# protocol may be either http or https
#push.gcm.proxy.protocol=
#push.gcm.proxy.host=
# negative value means default port
#push.gcm.proxy.port=-1
#push.gcm.proxy.user=
#push.gcm.proxy.password=

#   Push APNS proxy settings
#push.apns.proxy.enabled=false
# only SOCKS proxy is supported at the moment
#push.apns.proxy.type=SOCKS
#push.apns.proxy.host=
#push.apns.proxy.port=

推荐答案

好的,我已经检查了.

对于推送通知,Worklight使用 notnoop . Worklight中捆绑的当前版本在APNS代理中不支持用户名/密码(其类型为SOCKS,我不确定它是否也支持此方法).捆绑版本中不存在.

For Push Notifictions Worklight uses notnoop. The current version bundled in Worklight does not have username/password support in APNS proxy (which is of type SOCKS and I am not sure if it at all supports this method, either). It does not exist in the bundled version.

注意:无法在Worklight中升级notnoop,它已集成在其中.

Note: it is not possible to upgrade notnoop in Worklight, it is integrated within.

这篇关于IBM Worklight 5.0.6.1-通过代理服务器推送通知的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆