yes, it's a simple question. There are examples in the doc that cover this. but I know it's a
huge inconvenience to actually
read the documentation. so you ask me. let's see...
# convert www.mydomain.com/eventname to www.mydomain.com/default.aspx?id=eventname
RewriteRule ^/([^\./]+)$ /default.aspx?id=$1 [L]
# convert www.mydomain.com/eventname/info to www.mydomain.com/info.aspx?id=eventname
RewriteRule ^/([^\./]+)/info$ /info.aspx?id=$1 [L]
Ahhhh - I made a change to your request. Instead of exposing info.aspx on the 2nd type of URL, I made it just info. No need for a .aspx on that public URL. You can add the .aspx if you like, by inserting it back in the pattern at the appropriate spot. In
case you read none of the IIRF documentation, the "pattern" is the first argument to the RewriteRule directive.
Also you didn't describe the pattern for "eventname", so I used "any sequence of one or more characters, where each character is neither a dot nor a slash". this looks like "([^\./]+)" in a regex. If you want a stricter
definition for the eventname thing, you'll have to change that regex.
Here's the thing: as they say, a little knowledge is dangerous. You now have a couple rules that do "basically" what you asked for. But the internet is a hostile place. You will get "good" requests for the URLs that
match those rules, and those requests will be rewritten as you want. But you will also get a ton of "bad" URLs that also match those patterns. You may want to filter those bad URLs. And, there are probably many other kinds of URLs you
will want to handle. You should run tests to satisfy yourself that everything works.
You also need logging, and you need to decide on a log level . You should insert the StatusUrl directive. There are a bunch of other things to consider.
I can't give you the answers for that stuff. You have to do it yourself.