http://aspnetwebstack.codeplex.com/discussions/403529
Comments: We've investigated this issue and I've reported the results on the forum thread: http://aspnetwebstack.codeplex.com/discussions/403529 The short of it is: 1. It turns out to be a bug in ASP.NET itself, and we have logged a bug in the Microsoft internal bug database so that it will be tracked for a future release. 2. We believe we've found a workaround for this issue and I've posted it in the forum thread. If the workaround works, we will close out this issue because the bug is not in MVC itself.
Comments: We've investigated this issue and I've reported the results on the forum thread: http://aspnetwebstack.codeplex.com/discussions/403529 The short of it is: 1. It turns out to be a bug in ASP.NET itself, and we have logged a bug in the Microsoft internal bug database so that it will be tracked for a future release. 2. We believe we've found a workaround for this issue and I've posted it in the forum thread. If the workaround works, we will close out this issue because the bug is not in MVC itself.