Create URL Rewrite Middleware

[jkotalik]

Objectives:

• Add URL Rewrite for incoming PathStrings and QueryStrings
• Support Regex expressions on input and based on match modify output
• Add capture parameters within matching string to be used on modified output
• Add URL Redirect which on match would terminate (Ex http to https)

[jkotalik]

Implementation Proposal:

Create a new builder, UrlRewriteBuilder. This builder would, for example, have a method:
RewritePath(string regexCompare, Func<UrlRewriteContext, Task> onMatch)
which would add a rule for the HttpRequest's path string. The UrlRewriteContext will be used to store any information that was captured in the regex matching. When a HttpRequest comes in, if there is a regex match on the input's path string, the onMatch function would be called.

Users can provided their own onMatch function and have access to the UrlRewriteContext. We will also provide overloads/ methods to do certain tasks (Ex overloading RewritePath to take in two strings, with a regex string to convert the matched string appropriately).

[Cowlephant]

So I'm guessing with several months away for 1.1.0 release, we should be looking into one of the expressed alternative fixes?

[Tratcher]

Yes, it will be a few weeks before there's a working nightly build for this.

[jkotalik]

Use Cases and Extensibility :

• Redirecting from http to https
• Rewriting Path
• Redirecting Path
• Rewrite Query String
• Check existence of file/ directories
• Change any request field

[DaveSlinn]

This is not directly related, but I am currently using web.config url rewrite for my .net core web app and it works, but i want to use web.config transformations to add url rewrite entry for release build and publish and that doesn't seem to be working with .net core. Do .config transforms not work anymore with dotnet.exe publish?

[Tratcher]

No, config transforms are not supported.

[moozzyk]

You could actually try this: aspnet/IISIntegration#146 (comment)

[DaveSlinn]

Thanks for the suggestion - managed to use nil4's dotnet xdt package integrated into our build process (angular 2 app building on-premises and publishing to azure) - and is working fine. I'll keep an eye on this WIP in the coming weeks and see if it makes sense to transition over to UrlRewriteBuilder when it becomes available.