ISAPI_Rewrite 3.1.0.60

We are happy to announce the release of new build of ISAPI_Rewrite!

We have fixes some bugs related to:

• conversion of RewriteProxy directive from v2 syntax
• multiple Set-Cookie: headers processing in proxy extension
• PathInfo processing in proxy extension, that earlier caused problems with some AJAX apps and web services

and added some new features:

• now error.log and rewrite.log correctly display Unicode characters
• option to set/unset .htaccess Hidden attribute optionally.

Notice that latest builds of ISAPI_Rewrite operate on Windows Server 2008 R2 (IIS7).

In this build we attempted to meet some of our customers’ frequently requested features. If you see any other possibilities to make our products better, please don’t hesitate to write proposals into Comments.

Subtleties of Unicode transformation in IIS6

Today we want to give you a brief info on what and how is being encoded in IIS6.

When IIS gets a request (e.g. GET /smth), each Unicode character of "smth" should be encoded as %xx in UTF-8 (in our case: GET /%73%6d%74%68).

However, IIS also recognizes non-encoded Unicode (UTF-8, UTF-16, etc.) text (e.g. GET /Şмŧĥ) which it will then convert to UTF-8 equivalent.

In it's turn native encoding for Windows API is UTF-16, thus the request is encoded once again (from UTF-8 to UTF-16). That's why ISAPI module also operates with UTF-16.

To return result to IIS rewritten request should be encoded back to UTF-8 and escaped as %xx because ISAPI does not provide native Unicode API.