urlrewriter

I have the following rule: <rule> <from>^/users/(.*)$</from> <to last="true">/users.do$1</to> </rule> And I want to match the following url: http://localhost:8077/users/?elemsPerPage=10 and redirect it to: http://localhost:8077/users.do?elemsPerPage=10 The problem is that when the url rewriter engine finds the "?" character in the url it does not return anything else in the $1 matched parameter. Neither it adds the parameters to the query string. Any ideas? Finally I've found a way to solve this: Rule: <rule> <from>^/users/$</from> <to last="true">/users.do?%{query-string}</to> </rule> There

I have this page: http://mysite.org/myapp/pages/blog?name=user9 and I need to have this: user9.mysite.org What should i write in my routes.py? Ok, so i think misinterpreted this a little. You need user9.mysite.org to be served from the web2py app. One way, if you have your site hosted at mysite.org, is to pass all requests (regardless of subdomain) to the web2py application (you'll need an A record like *.mysite.org with your DNS provider: http://kb.mediatemple.net/questions/791/DNS+Explained#/A_Record ) Then, you can use routes Something like: routes_in = ( ('http://(?P<user>.*).mysite.org/(

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. I've looked at several URL rewriters for ASP.Net and IIS and was wondering what everyone else uses, and why. Here are the ones that I have used or looked at: ThunderMain URLRewriter : used in a previous project, didn't quite have the flexibility/performance

I have a query string parameter value that contains an ampersand. For example, a valid value for the parameter may be: a & b When I generate the URL that contains the parameter, I'm using System.Web.HTTPUtility.UrlEncode() to make each element URL-friendly. It's (correctly) giving me a URL like: http://example.com/foo?bar=a+%26b The problem is that ASP.NET's Request object is interpreting the (encoded) ampersand as a Query String parameter delimiter, and is thus splitting my value into 2 parts (the first has "bar" as the parameter name; the second has a null name). It appears that ASP.NET is