IIS7 - URL Rewrite Module

Re: ASP.NET detected invalid characters in the URL

DanielVL — Thu, 20 Nov 2008 20:08:35 GMT

I think your rule will rewrite from http://microsoft.com/somePage.aspx to http://microsoft.com:80/somePage.aspx

{R:0} will be expanded "/somePage.aspx"

Please use FRT to see how the rewriting is executed:

http://learn.iis.net/page.aspx/467/using-failed-request-tracing-to-trace-rewrite-rules/

Thanks.

Re: ASP.NET detected invalid characters in the URL

k_sega — Tue, 18 Nov 2008 22:30:43 GMT

Thank you for quick response.

Yes, I've rechecked - I use latest version of these extensions.

As far as I understand if I'll set following rule:

URL Rewriter will sent me from http://microsoft.com/somePage.aspx to http://microsoft.com:80/http://microsoft.com/somePage.aspx and then ARR will correctly process it, sending request to microsoft server.

But in this scenario any managed module will try to parse second link, will get incorrect symbols and fail.

Am I right? So, is it ARR issue?

Re: ASP.NET detected invalid characters in the URL

DanielVL — Tue, 18 Nov 2008 17:04:38 GMT

I'm not familiar with this issue, but before going on, Did you make sure to install the latest ARR+Rewrite releases?

http://www.iis.net/extensions/ApplicationRequestRouting

http://www.iis.net/extensions/urlrewrite

Thanks.

ASP.NET detected invalid characters in the URL

k_sega — Tue, 18 Nov 2008 16:14:21 GMT

In the post http://forums.iis.net/t/1152682.aspx I've described situation when URL Rewriter + ARR do not allow managed module to work.

Any managed module causes

400.0 error whith "ASP.NET detected invalid characters in the URL"

with exception in event log:
at System.Web.Security.CookielessHelperClass.RemoveCookielessValuesFromPath()
at System.Web.HttpContext.Init(HttpRequest request, HttpResponse response)
at System.Web.HttpContext..ctor(HttpWorkerRequest wr, Boolean initResponseWriter)
at System.Web.Hosting.PipelineRuntime.CreateContext(IIS7WorkerRequest wr, IntPtr nativeRequestContext)

Seems that path is empty in that situation. Is it bug of URL Rewriter, or it is ARR problem?