Http 400 on pull - but only with newer versions

[Aaron Lawrence]

Hi all,

I was running TortoiseHg 4.8.2. On our largest repo (16,000 commits, 6GB) I started getting a HTTP 400 error when pulling.
Fiddler proxy showed HTTP Error 400. The size of the request headers is too long.

I noticed that going back to TortoiseHg 3.7.3 actually stopped the problem happening.
Now I'm running with 3.7.3 and it seems fine. Other people are also using older Hg with the same repo and not having any problem.

We don't want to be stuck on an old version of Mercurial though.

I found people talking about having too many dangling heads. Our repo has 200 topological heads, which seems well below what others had problems with. But more importantly, when I got rid of 50 of them my merging to a graveyard branch, it didn't help, the 400 error kept happening with 4.8.2.

If I did a fresh clone, it would work for a little while then start giving 400 errors again.
I could see that the headers went from ~8k to 26k without anything changing.

So I don't know what to think - why would older mercurial work better? Why does the header request size increase after a few pulls?

Our server is an old version of Kiln, 2.9.61.0 (DB 202)  running on IIS.

Thanks for any help
Aaron



Aaron Lawrence  |  Senior Software Developer

[A86BD442-0495-4DDC-B128-79BACF3FE8CA]

Phone: 06 356 4120
Skype: umj_aaron.lawrence
aaron.lawrence at umajin.com<mailto:aaron.lawrence at umajin.com>
umajin.com<http://www.umajin.com/>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial/attachments/20190321/d3cd213d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2927 bytes
Desc: image001.png
URL: <http://www.mercurial-scm.org/pipermail/mercurial/attachments/20190321/d3cd213d/attachment.png>