使用 HttpRequestMessageProperty 和 OperationContextScope 的 WCF HTTP 标头

发布于 2024-12-01 01:29:53 字数 965 浏览 1 评论 0 原文

我意识到这是一个被反复问到的问题，但我找不到可以查看的“陷阱”列表。

我正在编写一个 WCF 客户端，该客户端将使用 SAP Web 服务，在 web.config 中使用 customBinding，将allowCookies 设置为 false 并启用对可靠会话的支持。我将 HTTP 标头设置如下：

var authCookie = new System.Net.Cookie();
var wcfClient = new SomeWcfClient();
using (var context = new OperationContextScope(wcfClient.InnerChannel))
{
    var cookies = new CookieContainer();
    cookies.Add(authCookie);
    var endPoint = new EndpointAddress("http://someDomain.test/");

    var httpRequest = new System.ServiceModel.Channels.HttpRequestMessageProperty();
    OperationContext.Current.OutgoingMessageProperties.Add(System.ServiceModel.Channels.HttpRequestMessageProperty.Name, httpRequest);
    httpRequest.Headers.Add(HttpRequestHeader.Cookie, cookies.GetCookieHeader(endPoint.Uri));

    wcfClient.PerformOperation();
}

当我使用 Fiddler 时，我的 HTTP 标头不会出现。我也尝试过创建虚拟 Referer 和 User-Agent 标头，认为我的 cookie 标头可能发生了一些特定的情况，但即使是其他标头也没有出现。有什么想法吗？接下来我该看哪里？

原文

I realize this is a question that's been asked time and again, but I can't find a list of "gotchas" that I can take a look at.

I'm writing a WCF client that will consume an SAP web service, using a customBinding in my web.config with allowCookies set to false and support for reliable sessions enabled. I'm setting my HTTP headers as follows:

var authCookie = new System.Net.Cookie();
var wcfClient = new SomeWcfClient();
using (var context = new OperationContextScope(wcfClient.InnerChannel))
{
    var cookies = new CookieContainer();
    cookies.Add(authCookie);
    var endPoint = new EndpointAddress("http://someDomain.test/");

    var httpRequest = new System.ServiceModel.Channels.HttpRequestMessageProperty();
    OperationContext.Current.OutgoingMessageProperties.Add(System.ServiceModel.Channels.HttpRequestMessageProperty.Name, httpRequest);
    httpRequest.Headers.Add(HttpRequestHeader.Cookie, cookies.GetCookieHeader(endPoint.Uri));

    wcfClient.PerformOperation();
}

When I use Fiddler, my HTTP header does not come across. I've tried creating dummy Referer and User-Agent headers, too, thinking that maybe something specific was happening with my cookie header, but even those other headers did not come across. Any thoughts? Where should I look next?

分享到QQ

分享到微博