Bug 11336 - OperationContext.Current.OutgoingMessageProperties not setting HTTP request headers
Summary: OperationContext.Current.OutgoingMessageProperties not setting HTTP request h...
Alias: None
Product: Class Libraries
Classification: Mono
Component: WCF assemblies ()
Version: 2.10.x
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-03-21 17:08 UTC by Matt Clay
Modified: 2014-01-10 05:04 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

This program shows how an HTTP request header is not created under Mono, but is under Microsoft .NET. (2.77 KB, text/plain)
2013-03-21 17:08 UTC, Matt Clay

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Matt Clay 2013-03-21 17:08:58 UTC
Created attachment 3678 [details]
This program shows how an HTTP request header is not created under Mono, but is under Microsoft .NET.

Under Microsoft .NET you can use a HttpRequestMessageProperty to add HTTP request headers to a WCF service call by adding it to OperationContext.Current.OutgoingMessageProperties inside an OperationContextScope.  Under Mono, this does nothing.
Comment 1 Matt Clay 2013-03-21 19:54:25 UTC
It turns out that some HTTP request headers can be set.  The problem lies in Mono's HttpRequestChannel.BeginProcessRequest method.  That method is filtering out certain HTTP headers using WebHeaderCollection.IsRestricted.

My original tests used the UserAgent header, which are on the restricted list.  If you use "X-UserAgent" instead, the problem goes away.

To fix this, the call to WebHeaderCollection.IsRestricted needs to be removed, although special handling for some of the previously filtered headers may be required.
Comment 2 Matt Clay 2013-03-21 20:20:09 UTC
Correction: I meant "User-Agent" not "UserAgent" is on the restricted list.
Comment 3 Atsushi Eno 2014-01-10 05:04:33 UTC
fixed [master 2fd8da4]