No. Rename it iis-urlrewrite and create a separate url-rewriting tag.

It sounds like there are two aspects there: URL rewriting, which is general, and IIS, which this question was specifically about and/or does something special with URL rewriting. Should there be two tags, url-rewriting and iis, both applied to this question but might be used separately in other contexts?

@Monica Cellio - yes, you are right: there are two aspects. I would use url-rewritting + iis.

@MonicaCellio No, UrlRewrite is a specific URL rewriting engine.

@Moshi UrlRewrite is an engine but URL rewriting is a more general practice. Should the engine have its own tag or is that too specific? I don't know. (I mean, would we have a ClassNotFoundException tag as opposed to "exceptions" and maybe "class-loader"?)

@MonicaCellio I personally don't mind it having its own tag. There's no harm I having both IIS UrlRewrite and URL rewriting as two tags, right?

@Moshi [iis-urlrewrite] can be defined, but I would try to keep tags count as low as possible. By using [iis] and [url-rewritting], we have only two tags that are quite reusable.

@Alexei I don't really see the need to remove tags unless people start running out of space for more relevant tags