白标提供商建议
我开发了一个提供相当基本服务的网站。用户注册、填写在线表格、付款，然后根据表格中的数据生成一些 pdf 文档。他们可以再次登录，下载文档等。没什么了不起...
开发这些网站是为了根据查询字符串参数更改其品牌（人们将服务转售为自己的服务）。到目前为止，这种方式一直运行良好，但是越来越多的人想要完整的白标服务。好的旧查询字符串方法不够透明，因为用户可以很容易地看到“真实”域。
我考虑过查看主机名而不是品牌标识符的查询字符串，这很容易在 IIS 中的站点下添加主机名。问题是该网站必须在 SSL 下运行（每个 IP 1 个证书等...）。
那么，实现这一目标的最佳方法是什么？您能否获得并非全部基于一个域的多个域证书（例如 extra.test.com 和 www.simple.co.uk）？我已经设置了通配符 SSL 证书。在使用旧的元数据库编辑技巧之前，在 IIS 中，但是通配符都是一个域。
有没有一些代理工具可以处理这个魔法？我显然将任何内容重新编码为必要的，我只是确定有人已经考虑过这一点了！
I've developed a website that provides a fairly basic service. Users register, fill in online forms, make a payment and then generate some pdf documents based on the data in the forms. They can log in again, downlod documents etc. Nothing amazing...
The sites been developed to change its branding based on a query string parameter (people resell the service as their own). This has been working OK up to now, however more and more people are wanting a full white label service. The good old querystring method isn't transparent enough as users can quite easily see the 'real' domain.
I have thought about looking at the host name rather than the querystring for my branding identifier, easy enough to add a host name under the site in IIS. The issue with this is the site has to run under SSL (1 certificate per IP etc...).
So, whats the best way to achieve this? Can you get multiple domain certificates that aren't all based on the one domain (e.g. extra.test.com & www.simple.co.uk)? I've set up wildcard SSL certs. in IIS before using the old Metabase edit trick, however the wildcard is all one domain.
Is there some proxy tool to will handle the magic? I obviously recode whatever as nessisary, I'm just sure someone must have thought about this already!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您的 SSL 证书绑定到单个域。除非您使用通配符证书，在这种情况下，它们会绑定到某个公共根，并且您可以拥有不同的子域。
我认为你在这里想要实现的目标是不可能的。
我的建议是，如果您的客户需要自己的 SSL 透明 URL，您可以将其纳入您向他们收取的服务费用中。
祝你好运！
Your SSL certs are tied to a single domain. Unless you go with a wildcard cert in which case they're tied to some common root and you can have varying subdomains.
I don't think what you're trying to achieve here is possible.
My suggestion would be that if your customers are demanding their own transparent URLs with SSL, you work that into what you're billing them for the service.
Good luck!