Mercurial server using IIS7 and CGI - Bad Gateway error if cloning to a specific revision

[Eduard Stefan]

Hi,

I have set up Mercurial 1.6.2 on IIS 7/CGI using
  http://www.jeremyskinner.co.uk/mercurial-on-iis7/

In order to successfully clone a repo I must check "Use uncompressed transfer"
and not select any target revision.

If I select a target revision ("Clone to revision") or uncheck "Use
uncompressed transfer"
I get the following error:

  requesting all changes
  HTTP Error 502: Bad Gateway

When I try to clone to revision 1 of a test repo the response from the
CGI script is:

  2 changesets found
  Status: 200 Script output follows
  Content-Type: application/mercurial-0.1
  <blank line>
  <blank line>

The URL used for the request seems to be (broken in multiple lines):

  https://127.0.0.1:44300/hgweb.cgi/django/?
  bases=0000000000000000000000000000000000000000&amp;
  cmd=changegroupsubset&amp;
  heads=9db35fb5f525eab1f709b9c41441a30ab7e992b8

The browser output to this URL is:

  HTTP Error 502.2 - Bad Gateway
  The specified CGI application misbehaved by not returning
  a complete set of HTTP headers. The headers it did return are
  "2 changesets found Status: 200 Script output follows Content-Type:
application/mercurial-0.1 ".

Is there a workaround for this behavior? After cloning the repo I can
push/pull as usual
(including bookmarks). Also, the web interface is working ok.

Have a nice day,
  Eduard