Comments on: Manipulating HTTP Headers in your WCF Message

By: Kenny

Kenny — Mon, 25 Aug 2008 16:46:52 +0000

Saran, does your code work if you aren’t adding the HTTP header? This doesn’t sound like an HTTP-related issue.

Steve, you can add a ClientMessageInspector via a behavior to do what you intend.

By: Steven Pack

Steven Pack — Thu, 21 Aug 2008 07:25:22 +0000

Hi Kenny,

Thanks for the sample. Is there any way to have that code execute for every call to the client? I’m trying to do exactly what you are doing there, but with an interceptor/inspector/behavior defined in configuration.

Steve

By: Saran

Saran — Thu, 03 Jul 2008 11:20:03 +0000

Hi,
When I tried your code snippet, the connection is getting closed abruptly. Using the wcftestviewer.exe, I
am seeing the following details in the log file.
The Exception type: EndpointNotFoundException. The message is There was no channel that could accept the message with action.

The warning message says that,
The incoming message is not part of the existing security session.

Any help?

Thanks,
Saran

By: Kenny

Kenny — Sat, 03 May 2008 18:25:18 +0000

Is this on your request or response? I would recommend posting on the WCF forum for this question.

By: Marshall Brooke

Marshall Brooke — Wed, 19 Mar 2008 11:10:47 +0000

Hi Kenny,

Do you know why the Cache-Control header is always overwritten with plain ol “private” no matter what you set it as.

best

Marshall

By: kennyw.com » Blog Archive » Suppressing Expect 100-Continue on your Requests

Thu, 16 Nov 2006 02:33:02 +0000

[...] WCF has a very powerful extensibility mechanism around modifying HTTP headers. However, you will get tripped up if you try and modify the “Expect: 100-Continue” header on outgoing requests. This is because System.Net will (by default) add this header on outgoing requests. [...]