Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
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.
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.
Correction: I meant "User-Agent" not "UserAgent" is on the restricted list.
fixed [master 2fd8da4]