no content-type error

[Mads Kiilerich]

On 06/12/2014 11:45 AM, Ole Keiser Christensen wrote:
> Hi
>
> I have for last 2 weeks trying to figure out why 2 of our repos fails 
> to do pull's...
> we did receive the some early indications that something was wrong 
> when we received following error:
> HTTP Error 400 Bad Gateway
>
> we noticed that it could relate to some settings related to the 
> request header, so we added following keys to the Registry:
>
> MaxFieldLength - set with max values
> MaxRequestBytes - set with max values
>
> it did remove the previous error, just to show us a new one which we 
> also think relates to the size of the request header..
>
> it is possible to clone the repo from scratch, but when you try to do 
> a pull, you are presented with following error:
>  does not appear to be an hg repository:
> ---%<--- (no content-type)
>
> ---%<---
>
> apparently the request header is empty or truncated when we do the pull...
> on that we also receive a status 200 from the server that everything 
> is ok.
>
> a look in the IIS log doesn't show any thing the could indicate some 
> problems
>
>
> Our system is running on Windows2008R2x64 and has done that for the 
> past 2 years without problems..
> we are using Python 2.7.6 64 bit and compile the latest Mercurial 
> Source (3.0.1) with that..
> our clients uses several versions of TortoisHG
>
> mercurial is using an IIS webserver with an ISAPI module..
>
> one of the repos do contain a great amount of History, Branches and 
> files...
>
> here are some data for repo 1:
>
> windows properties:
> Size: 951 mb
> Size on disk: 1.99 GB
> Contains: 18913 files
>
> no subrepos.
>
> it does however contains a fair amount of branches.
>
> 203 branches.
> were only 8 of them are open.

There _must_ be something in the server error logs somewhere.

Try and see if you can reproduce the problem with 'hg serve --web-conf 
...' .

If you are right that it is a problem with the request size, you might 
be hitting essentially the same as for instance 
http://mercurial.markmail.org/thread/mwawuk6m57xj6ofl (and with the same 
options for workaround), only hitting limitations of 
http://selenic.com/repo/hg/rev/ce99d887585f . Your repo is not so big 
that it should cause problems ... but some IIS layer might have some 
limitations. You could try to do some network sniffing to see how big 
the headers are when they cause problems.

/Mads
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20140612/da621ebc/attachment.html>