http://blogs.msdn.com/drnick/archive/2006/07/27/It-Hurts-When-I-Set-the-User-Agent.aspxConsider the following simple test server that uses no WCF code at all. using System; using System.Net; class Server { static void Main( string [] args) { HttpListener listener = new HttpListener(); listener.Prefixes.Add( "http://localhost:1000/" ); listener.Start();enCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/drnick/archive/2006/07/27/It-Hurts-When-I-Set-the-User-Agent.aspx#681093Fri, 28 Jul 2006 06:24:58 GMT91d46819-8472-40ad-a661-2c78acb4018c:681093Jason Haleyhttp://blogs.msdn.com/drnick/archive/2006/07/27/It-Hurts-When-I-Set-the-User-Agent.aspx#701580Tue, 15 Aug 2006 23:50:01 GMT91d46819-8472-40ad-a661-2c78acb4018c:701580scott oDropped but still available: <br> <br>HttpListenerContext context = listener.GetContext (); <br>HttpListenerRequest request = context.Request; <br> <br>Console.WriteLine (&quot;{0}&quot;, request.UserAgent); <br>http://blogs.msdn.com/drnick/archive/2006/07/27/It-Hurts-When-I-Set-the-User-Agent.aspx#701701Wed, 16 Aug 2006 01:42:21 GMT91d46819-8472-40ad-a661-2c78acb4018c:701701Nicholas AllenThat's what you do if you have access to the request object. &nbsp;The HTTP transport in WCF uses HttpListener internally but doesn't make the listener context visible. &nbsp;You have to wait for the framework to get updated even though the change in the framework is one line.