Bug 9133 - Route generation should be case-insensitive
Summary: Route generation should be case-insensitive
Status: RESOLVED FIXED
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Web ()
Version: master
Hardware: PC All
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-12-25 21:14 UTC by Daniel Lo Nigro
Modified: 2013-01-09 17:54 UTC (History)
2 users (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Daniel Lo Nigro 2012-12-25 21:14:47 UTC
Values in the Defaults RouteValueDictionary should be case-insensitive, as they are case-insensitive on Microsoft .NET.

Given a route like this:
var route = new Route ("HelloWorld", new MyRouteHandler ()) {
	Defaults = new RouteValueDictionary (new {controller = "Home", action = "HelloWorld"})
};

The following should work:
var lowercase = route.GetVirtualPath (rc, new RouteValueDictionary
{
	{"controller", "home"},
	{"action", "helloworld"}
});
Comment 1 Daniel Lo Nigro 2012-12-25 21:28:28 UTC
Pull request sent: https://github.com/mono/mono/pull/527
Comment 2 Andres G. Aragoneses 2013-01-09 16:01:32 UTC
This bug should be marked as FIXED, no?
Comment 3 Daniel Lo Nigro 2013-01-09 17:54:34 UTC
Correct - I must have forgotten to change the status.