Feb 08, 2008 03:54 PM|developmentalmadness|LINK
The problem with that approach is that if I set the cookie value from one browser session then the value changes for all browser sessions. Which is why I need the value to be in the url.
In any case, I have misunderstood how default values work. Here's a quote from Scott Guthrie about default values: "The "Defaults" property on the Route class defines a dictionary of default values to use in the event that the incoming URL doesn't include
one of the parameter values specified." So defaults will be passed to an action method that expects that parameter when the value doesn't exist in the url.
What we need (if anyone is listening) is a way to hook into the url building process (RouteCollection.GetUrl) and manipulate the output. For now, I think I'll look into an extension method on HtmlHelper for methods that call GetUrl and use those in place
of the existing methods.