Logging HTTP transport headers

Is there a way to log out HTTP transport headers when httpTransport is used?
Clearly it is possible to print out HTTP headers of an inbound messages (ex:
service side) by examining
message.Properties[HttpRequestMessageProperty.Name].Headers, but it does not
look it is possible to print them out for outbound messages (ex: client
side). Sounds to me that the reason there is asymmetry here is because for
inbound messages transport channel is the first one, while for outbound it
is the last one, and WCF team did provide any hooks in this standard
httpTransport channel to find out which exactly HTTP headers it is about to
be sent. Am I right?

Interestingly enough there is always a way to find out exactly what will be
the body (exact byte array) by using custom encoder that just wraps standard
"internal" one and gets a chance to log exact body byte array.

Thankx.

Check http://msdn2.microsoft.com/en-us/library/ms751526.aspx
Arkady

"AVS" <avslivker@yahoo.com> wrote in message
news:%23GQjf$lSHHA.4260@TK2MSFTNGP06.phx.gbl...
> Is there a way to log out HTTP transport headers when httpTransport is
> used?
> Clearly it is possible to print out HTTP headers of an inbound messages
> (ex: service side) by examining
> message.Properties[HttpRequestMessageProperty.Name].Headers, but it does
> not look it is possible to print them out for outbound messages (ex:
> client side). Sounds to me that the reason there is asymmetry here is
> because for inbound messages transport channel is the first one, while for
> outbound it is the last one, and WCF team did provide any hooks in this
> standard httpTransport channel to find out which exactly HTTP headers it
> is about to be sent. Am I right?
>
> Interestingly enough there is always a way to find out exactly what will
> be the body (exact byte array) by using custom encoder that just wraps
> standard "internal" one and gets a chance to log exact body byte array.
>
> Thankx.
>

This does not help. HTTP headers do not get printed even if
logMessagesAtTransportLevel="true" and <sourcce ... switchValue="Verbose">


"Arkady Frenkel" <arkadyf@hotmailxdotx.com> wrote in message
news:%23GUbjqoSHHA.2124@TK2MSFTNGP06.phx.gbl...
> Check http://msdn2.microsoft.com/en-us/library/ms751526.aspx
> Arkady
>
> "AVS" <avslivker@yahoo.com> wrote in message
> news:%23GQjf$lSHHA.4260@TK2MSFTNGP06.phx.gbl...
>> Is there a way to log out HTTP transport headers when httpTransport is
>> used?
>> Clearly it is possible to print out HTTP headers of an inbound messages
>> (ex: service side) by examining
>> message.Properties[HttpRequestMessageProperty.Name].Headers, but it does
>> not look it is possible to print them out for outbound messages (ex:
>> client side). Sounds to me that the reason there is asymmetry here is
>> because for inbound messages transport channel is the first one, while
>> for outbound it is the last one, and WCF team did provide any hooks in
>> this standard httpTransport channel to find out which exactly HTTP
>> headers it is about to be sent. Am I right?
>>
>> Interestingly enough there is always a way to find out exactly what will
>> be the body (exact byte array) by using custom encoder that just wraps
>> standard "internal" one and gets a chance to log exact body byte array.
>>
>> Thankx.
>>
>
>