I'm using HttpContext.Current.RewritePath to change a URL that looks like this:

domain.com/<userid>/<roomname>

Into a URL that looks like this:

domain.com/Room.aspx?userID=<userid>&roomName=<roomname>

That bit works fine.  But in Room.aspx, I was then expecting to be able to access the QueryString parameters just like normal, i.e.:

string userID = Request.QueryString["userID"];
string roomName = Request.QueryString["roomName"];

However, despite the fact that it's been rewritten, the "Request" object still has only the old information about the original, non-rewritten request, i.e., Request.Path = "/someuserid/someroomname", not "Room.aspx?userID=someuserid&roomName=someroomname".  That makes it just a tad bit trickier to pull out the parameters, since you have to do string parsing, but if you have multiple different URL structures that all map to the same .aspx page, it makes it kinda tricky to figure out which ones are which.

Am I missing something here, or is this how it's intended to work?

sample code for url rewrite:  http://mytechnicalcorner.blogspot.com/2008/11/rewrite-url-with-masterpage.html

If I understand your code correctly, that's how I expected it to work, i.e., you can actually do something like this:

<rule source="(\w*)/(\w+)/?" destination="Room.aspx?ownerUserID=$1&amp;roomName=$2" />

However, the code that I'm using (borrowed from here: http://www.simple-talk.com/dotnet/asp.net/a-complete-url-rewriting-solution-for-asp.net-2.0/) doesn't seem to work that way.  Here's a snippet:

// new path to rewrite to
string rew = cfg.RewriteBase + path;
// save original path to HttpContext for further use
HttpContext.Current.Items.Add("OriginalUrl", HttpContext.Current.Request.RawUrl);
// rewrite
Debug.WriteLine(string.Format("Rewriting {0} to {1}", HttpContext.Current.Request.Path, rew));
HttpContext.Current.RewritePath(rew);

Am I doing anything wrong?