blocks|key|1794976|text|看看这里：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1794977|http://web.archive.org/web/20080721055556/http://blog.magenic.com/blogs/jons/archive/2007/05/04/The-Tao-of-Microsoft-WCF-CustomBinding-Configuration-Elements.aspx|offset|length|1794978|这里详细讨论了在http连接期间操作keep+alive属性。|1794979|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|4I|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

Take a look here: 

<a href="http://web.archive.org/web/20080721055556/http://blog.magenic.com/blogs/jons/archive/2007/05/04/The-Tao-of-Microsoft-WCF-CustomBinding-Configuration-Elements.aspx" rel="nofollow noreferrer">http://web.archive.org/web/20080721055556/http://blog.magenic.com/blogs/jons/archive/2007/05/04/The-Tao-of-Microsoft-WCF-CustomBinding-Configuration-Elements.aspx</a>

There is a detailed discussion of manipulating the keep alive property during an http connection.

blocks|key|1795159|text|这个怎么样？似乎这可能是您的IIS服务器的一个功能，而与WCF服务无关？我知道这个链接适用于IIS6，但也许它可以作为IIS7？http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/73566f83-c257-4941-8ed8-7ae45b2e7985.mspx?mfr=true中类似内容的基础|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1795160|entityMap|0|LINK|mutability|MUTABLE|url|http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/73566f83-c257-4941-8ed8-7ae45b2e7985.mspx?mfr=true^0|1S|3H|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

How about this? Seems it may be a function of your IIS Server and nothing to do with the WCF service? I know this link applies to IIS6, but maybe it serves as a foundation to something similar in IIS7?
<a href="http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/73566f83-c257-4941-8ed8-7ae45b2e7985.mspx?mfr=true" rel="nofollow noreferrer">http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/73566f83-c257-4941-8ed8-7ae45b2e7985.mspx?mfr=true</a>

blocks|key|2008852|text|在我看来，您似乎想要调整Keep-Alive+HTTP头。您应该阅读HTTP+keep-alive上的this+article，并首先确定这是否真的值得您花时间。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2008853|如果是，请尝试创建Message+Inspector。这应该允许您修改发出的每条消息的HTTP标头：|2008854|public+class+KeepAliveMessageInspector+:+IClientMessageInspector
{
++++//+...

++++public+object+BeforeSendRequest(
++++++++ref+System.ServiceModel.Channels.Message+request,
++++++++System.ServiceModel.IClientChannel+channel)
++++{
++++++++//+Add/modify+the+Keep-Alive+header
++++++++var+httpRequestMessage+=+new+HttpRequestMessageProperty();
++++++++httpRequestMessage.Headers.Add("Keep-Alive",+"9000");
++++++++request.Properties.Add(
++++++++++++HttpRequestMessageProperty.Name,+httpRequestMessage);
++++++++return+null;
++++}

++++//+...
}|code-block|syntax|javascript|2008855|entityMap|0|LINK|mutability|MUTABLE|url|http://web.archive.org/web/20110605181241/http://www.io.com/~maus/HttpKeepAlive.html|1|http://msdn.microsoft.com/library/System.ServiceModel.Dispatcher.IClientMessageInspector.aspx^0|C|A|1F|C|0|0|9|H|1|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|F|3|G|5|6|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|H|3|I|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]|U|$5|P|Q|R|E|$S|V]]]]

It sounds to me like you're wanting to adjust the <code>Keep-Alive</code> HTTP header. You should read <a href="http://web.archive.org/web/20110605181241/http://www.io.com/~maus/HttpKeepAlive.html" rel="nofollow noreferrer">this article</a> on HTTP keep-alive and first determine if this is really something worth your time.

If it is, try creating a <a href="http://msdn.microsoft.com/library/System.ServiceModel.Dispatcher.IClientMessageInspector.aspx" rel="nofollow noreferrer">Message Inspector</a>. This should allow you to modify the HTTP headers for each message that gets sent out:

<pre><code>public class KeepAliveMessageInspector : IClientMessageInspector
{
 // ...

 public object BeforeSendRequest(
 ref System.ServiceModel.Channels.Message request,
 System.ServiceModel.IClientChannel channel)
 {
 // Add/modify the Keep-Alive header
 var httpRequestMessage = new HttpRequestMessageProperty();
 httpRequestMessage.Headers.Add("Keep-Alive", "9000");
 request.Properties.Add(
 HttpRequestMessageProperty.Name, httpRequestMessage);
 return null;
 }

 // ...
}
</code></pre>

blocks|key|2008904|text|我找到了解决这个问题的办法。问题是底层内核http.sys有它自己的超时，它会中断连接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2008905|http://mmmreddy.wordpress.com/2013/07/11/wcf-use-of-http-transport-sharing-persistent-tcp-sessions/

netsh+http+add+timeout+timeouttype=idleconnectiontimeout+value=120|code-block|syntax|javascript|2008906|此外，此问题与此What+130+second+timeout+is+killig+my+WCF+streaming+service+call?类似|offset|length|2008907|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/14266854/what-130-second-timeout-is-killig-my-wcf-streaming-service-call^0|0|0|8|1S|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

I found the solution for this. The problem is that the underlying kernel http.sys has it's own timeout and it will break the connection.

<pre><code>http://mmmreddy.wordpress.com/2013/07/11/wcf-use-of-http-transport-sharing-persistent-tcp-sessions/

netsh http add timeout timeouttype=idleconnectiontimeout value=120
</code></pre>

Also, this question is similar to this <a href="https://stackoverflow.com/questions/14266854/what-130-second-timeout-is-killig-my-wcf-streaming-service-call">What 130 second timeout is killig my WCF streaming service call?</a>

blocks|key|2009003|text|通过设置ServicePoint.MaxIdleTime，您可以更改持久HTTP连接上默认的100秒空闲超时。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2009004|https://www.visualbasicplanet.info/windows-communication/configuring-http-connections.html|offset|length|2009005|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2I|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

Setting ServicePoint.MaxIdleTime should let you change the default 100 second idle timeout on the persistent HTTP connections.

<a href="https://www.visualbasicplanet.info/windows-communication/configuring-http-connections.html" rel="nofollow noreferrer">https://www.visualbasicplanet.info/windows-communication/configuring-http-connections.html</a>

Http transport channel in WCF uses persistent HTTP connections by default. How to control keep alive timeout for those connections? Default value is 100s. I found that value by monitoring application in Procmon. I haven't found any setting in http transport binding element which configures this timeout. Is there any .NET class which can control that timeout?

How to set keep alive interval for HTTP connection in WCF

服务器

默认情况下，WCF中的Http传输通道使用持久HTTP连接。如何控制这些连接的保持连接超时？默认值为100s。我通过监控Procmon中的应用程序发现了这一价值。我没有在http传输绑定元素中找到配置此超时的任何设置。有没有什么.NET类可以控制超时？

问如何在WCF中为HTTP连接设置保持连接间隔
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在WCF中为HTTP连接设置保持连接间隔EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在WCF中为HTTP连接设置保持连接间隔
EN