问题描述
当我使用TwiML发送命令，Twilio API（TwilioProxy / 1.1），使请求不支持SNI HTTPS上我的Apache服务器。
When I use TwiML to send commands, Twilio API (TwilioProxy/1.1) makes requests to my Apache server on HTTPS without SNI support.
我需要阻止非SNI客户端（ SSLStrictSNIVHostCheck在）我的服务器上，因为我用多个域多个SSL证书，他们都使用Twilio。
I need to block non-SNI clients (SSLStrictSNIVHostCheck On) on my server because I use multiple SSL certificates with multiple domains and they all use Twilio.
是否有可能使用具有SNI支持不同的API或替代方法，这将使符合SNI工作？
Is it possible to use a different API that has SNI support or a workaround that would make that work with SNI ?
推荐答案
我刚刚也有类似的问题。 Twilio工作正常使用SNI（CloudFlare的免费通用的SSL）到四月底到2015年，但突然停止工作。
I've just had a similar problem. Twilio was working fine with SNI (CloudFlare free Universal SSL) up to end April 2015, but suddenly stopped working.
Twilio支持说，TwilioProxy尚不支持SNI。这让我吃惊，因为它是符合SNI工作，直到最近。他们说，SNI支持的积压，他们希望支持它的未来。
Twilio support says that the TwilioProxy doesn't yet support SNI. This surprises me since it was working with SNI until recently. They say SNI support is on the backlog and they 'hope to support it in the future'.
一个解决办法可能是把CloudFlare的在你的服务器的非SNI前临，但是这是目前第一个站点$ 20和其他站点$ 5。
A workaround may be to put CloudFlare Pro in front of your server for non-SNI, but this is currently $20 for the first site and $5 for additional sites.
另外，其他的替代品（如Plivo）可能支持SNI。我们正在调查他们。他们价格比Twilio太多，但没有。
Alternatively, other alternatives (e.g. Plivo) may support SNI. I'm investigating them; they're cheaper than Twilio too but don't have TwiML.
这篇关于Twilio - TwiML符合SNI支持的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！