I assume you're hosting using WCF in your .NET "app"? If so, you would need write some custom MessageEncoder
implementation because WCF does not provide this out of the box. Luckily there is a sample in the SDK that you can use.
I actually just realized that this is only step one of two depending on whether or not your client is also WCF? While this will encode the message, it would require that your client be using a similarly configured decoder because that implementation will not set the HTTP headers that are necessary to signal that encoding has occurred to a "pure" HTTP client. So, if it's not a WCF client on the other side, in addition to encoding the message itself, you would need to use the WebOperationContext
to apply the appropriate Content-Encoding: gzip
header. Unfortunately you cannot do this within the MessageEncoder
implementation itself because it's too late in the process because by the time the MessageEncoder
is asked to write the message contents the message frame, in this case the HTTP headers, has already been written. So, you would also need additional behavior, in the form of an IOperationBehavior
, applied to your operations that sets the headers accordingly.