blocks|key|4385618|text|听起来，正如您所怀疑的那样，自托管服务正在截获对端口443的调用，然后IIS才能接收这些调用。快速检查您的IIS日志应该会确认是否发生了这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4385619|请注意，虽然您可以在端口80上运行多个域，但如果我没记错的话，您只能在端口443上使用一个域，所以像主机标题这样的东西不能用于HTTPS连接。|4385620|有没有办法通过IIS托管自托管服务？这可能会解决这个问题，并减轻您未来的管理负担。|4385621|编辑以下注释:如果您不能在IIS中托管，那么假设我是正确的，WCF服务正在拦截IIS的请求，这就是阻止流量通过的原因，那么您可能需要在您的WCF应用程序中添加一些东西，或者为基于HttpListener的传入流量创建(或找到一个现有示例)独立代理，并使用它来识别正在查找的服务请求并适当地中继它。当然，这种类型的代理服务也可以用来屏蔽扩展，因此您可以使用它将任何格式的外部url转发到适当的内部服务url。重要的是，在网络堆栈中，代理位于WCF和IIS的前面，因此它可以在请求被任一方拾取之前拦截它们。如果您正在编写自己的代码，那么HttpListener可能是一个很好的起点。|offset|length|4385622|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.net.httplistener.aspx^0|0|0|0|7E|C|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@$H|V|I|W|1|X]]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

It sounds as though, as you suspect, the self-hosted service is intercepting calls to port 443 before IIS can pick them up. A quick check of your IIS logs should confirm if this is what is happening.

Be aware that although you can run multiple domains on port 80, if I recall correctly you can only use one on port 443, so things like host headers don't work with HTTPS connections. This could also be contributing to your problem.

Is there any way you could host the self-hosted service through IIS instead? That might solve this problem and reduce your administrative burden in future. 

Edit following comments:
If you can't host in IIS then, assuming that I am correct that the WCF service is intercepting the requests for IIS and that is what is preventing the traffic getting through, then you may need to either add something to your WCF application or create ( or find an existing example of ) an independent proxy for incoming traffic based on HttpListener and use that to identify which service requests are looking for and relay it appropriately. Of course, this type of proxy service could also be used to mask extensions so you could use that to relay an external url of any format to the appropriate internal service url. The important thing is that the proxy sits ahead of both WCF and IIS in the network stack so it can intercept requests before they are picked up by either. If you are writing your own then <a href="http://msdn.microsoft.com/en-us/library/system.net.httplistener.aspx" rel="nofollow">HttpListener</a> would probably be a good starting point.

blocks|key|1035290|text|经过相当多的研究，我能够确定其中一个服务端点，即设置为模拟crossdomain.xml文件的REST端点正在抢占IIS。除此之外，一切都像预期的那样工作。我抛弃了那个端点，转而使用IIS来提供文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1035291|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

After quite a bit of research, I was able to determine that one of the service endpoints, a REST endpoint set to simulate a crossdomain.xml file was pre-empting IIS. Otherwise everything was working as expected. I ditched that endpoint and used IIS to serve the file instead.

I've got a self hosted WCF service, and an ASP .Net web site that need to run on the same machine. I've discovered that when the self hosted service is running, all calls to port 443 intended for IIS (based on IP and host header/SSL bindings) get routed to the WCF architecture, and so the website stops working as long as the self hosted service is running. It's effectively pre-empting IIS' ability to do it's job.

Note that IIS still works fine on other ports, like port 80. It's just over-eager on port 443. Not entirely sure whether this is a server issue or a code/wcf issue.

Use Port 443 for both self hosted wcf service and IIS at the same time

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个自我托管的WCF服务，和一个ASP .Net网站，需要在同一台机器上运行。我发现，当自托管服务运行时，所有针对IIS的端口443 (基于IP和主机头/SSL绑定)的调用都会路由到WCF体系结构，因此只要自托管服务正在运行，网站就会停止工作。它有效地抢占了IIS完成其工作的能力。请注意，IIS仍然可以在其他端口上...

问同时对自托管wcf服务和IIS使用端口443
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问同时对自托管wcf服务和IIS使用端口443EN