Yeah, looking at the sourcecode i absolutely agree that its wrong behavior. You should be able to call GetRouteData on the C1PageRoute as many times you want. As it is now, when you call it it sets a flag in the HttpContext.Items so the next time its called it will yield an error.
Just by looking at the Error message it seems like a try to workaround some problems which can occur when MVC player matches the same route as a C1Page, but its more like trying to ease out the symptoms and not the actual underlying cause.
Just by looking at the Error message it seems like a try to workaround some problems which can occur when MVC player matches the same route as a C1Page, but its more like trying to ease out the symptoms and not the actual underlying cause.