在面向服务的系统中我必须购买多少个 SSL 证书?
我正在使用 Ruby on Rails 3,我想了解一些信息以便购买 SSL 证书。
我在此 URL 处有一个 RoR 应用程序
pjtnam.com
,在该 URL 处有另一个 RoR 应用程序
users.pjtname.com
如果我从应用程序 pjtname.com
向应用程序 users.pjtname.com
发出 HTTPS 请求,如下所示(在此示例中,我使用 Typhoeus gem),
Typhoeus::Request.get(https://users.pjtname.com/sign_in)
并且我必须通过 HTTPS 协议接收响应,我必须购买多少个 SSL 证书?
更新
如果出现以下情况,我必须购买多少个 SSL 证书
我的
pjtname.com
和users.pjtname.com
应用程序位于不同的服务器上?我的应用程序是
pjtname1.com
和pjtname2.com
,它们位于不同的服务器上?
I am using Ruby on Rails 3 and I would like to know some information in order to buy SSL certificates.
I have a RoR application at this URL
pjtnam.com
and another RoR application at this URL
users.pjtname.com
If I make an HTTPS request from the application pjtname.com
to the application users.pjtname.com
like this (in this example I use the Typhoeus gem)
Typhoeus::Request.get(https://users.pjtname.com/sign_in)
and I must receive the response over HTTPS protocoll, how many SSL certificates I must buy?
UPDATE
How many SSL certificates I must buy if
my
pjtname.com
andusers.pjtname.com
applications are located on different server?my applications are
pjtname1.com
andpjtname2.com
and they are located on different server?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
如果做得好,只有一个; “*.pjtname.com”和“pjtname.com”的通配符证书(可以在单个证书中包含多个名称)。
虽然您可以获取“pjtname.com”和“users.pjtname.com”的证书,但当您稍后决定需要“mail.pjtname.com”或“chat.pjtname”时,这样的证书就不再足够了.com' 或其他任何名称。通配符将涵盖这些未来的情况。
回复:更新
服务是否位于不同的服务器上并不重要;只需将证书放在两台服务器上即可。
单个证书中可以同时拥有“foo.com”和“bar.com”,就像您可以同时拥有“pjtname.com”和“users.pjtname.com”一样。但是,获取 foo/bar 证书可能比获取 pjtname.com/users.pjtname.com 更困难。
此外,无论平台如何,这些答案都是正确的。
If done properly, just one; a wildcard certificate for '*.pjtname.com' and 'pjtname.com' (it's possible to include more than one name in a single certificate).
While you could instead get a certificate for 'pjtname.com' and 'users.pjtname.com', such a certificate would no longer be sufficient when you later decide you need a 'mail.pjtname.com' or a 'chat.pjtname.com' or whatever. The wildcard would cover these future cases.
re: update
It doesn't matter if services are located on different servers; just put the certificate on both servers.
It's possible to have both 'foo.com' and 'bar.com' in a single certificate, just like you can have both 'pjtname.com' and 'users.pjtname.com'. However, it might more difficult to acquire the foo/bar certificate than the pjtname.com/users.pjtname.com.
Also, these answers are true regardless of platform.