I opened a ticket with SW on this as well and they came back with this response:
Development team have been confirmed as a bug.
The fix is due for release in a future update, but there is no specific time frame for this release yet.
The issue is reproducible when configuring web site to direct IP address and non default port in IIS 7 on win2008.
There are two workarounds:
1) Change web site binding to "All unassigned" instead of direct IP address. Not sure if IIS7 allows to add http binding "All unassigned" and port 443 (we aren't able to do this on our environment), so please change port number as well (could be non default but also non 443).
2) Use default http port (80) for web site.
The first option worked for me. I did not try the second.