Yes, you are right: it is. The problem is that IIS and ASP.NET (in combination) make a bit of a mess of URLs if they are slightly non-trivial. There are even some pathological edge-cases where two very different urls inbound come back with the same
.Url if you look at it inside ASP.NET; go figure. For example,
/x?a=b. Even though it gets routed correctly, both of these end up with the url saying
It has annoyed me a few times, too, when browsing the c# tag only to end up back on c.
The good news is: I've found some tricks that allow me to do this properly - will be deployed next build. It definitely needed fixing - it was bad enough for c#, but for anything international it was positively bejiggered. Thanks for giving me a nudge to fix it.