Bug 4108 - HttpCapabilitiesBase.MajorVersion mismatch between mono & ms.net
Summary: HttpCapabilitiesBase.MajorVersion mismatch between mono & ms.net
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Web ()
Version: master
Hardware: All All
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-03-27 10:58 UTC by Pablo Ruiz García
Modified: 2012-05-24 16:56 UTC (History)
2 users (show)

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

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 Pablo Ruiz García 2012-03-27 10:58:56 UTC
Mono's current implementation of http / browser capabilites as found at HttpCapabilitiesBase, looks for a node "capability[name='majorver']" at the appropiate browser definition (*.browser files), while microsoft's side uses "capability[name='majorversion']".

This makes somewhat a nightmare sharing browsercaps definition files bewteen mono & ms.net..
Comment 1 Pablo Ruiz García 2012-04-05 14:29:05 UTC

I just sent a pull-request via github fixing this issue: https://github.com/mono/mono/pull/271

Comment 2 Miguel de Icaza [MSFT] 2012-05-24 16:56:34 UTC
Thanks fror the patch!