Solve and understand HTTP Error 414: Request-URI Too Large

[Steve Barnes]

On 26/08/14 17:43, Mads Kiilerich wrote:
> On 08/26/2014 01:44 PM, Daniel Siepmann wrote:
>> Hello everyone,
>>
>> the error "HTTP Error 414: Request-URI Too Large" occurs regularly on 
>> our project.
>> We develop new features in their own branches and some colleagues 
>> don't close them.
>> If someone in our team doesn't pull often, he will get the error 
>> "HTTP Error 414: Request-URI Too Large".
>>
>> We raised the limits on our web server, but I want to understand why 
>> this problem exists.
>> How does mercurial generate the URLs for a pull-Request? Why does 
>> this url become longer and longer over time?
>> And is there a way to solve this problem instead of raising the 
>> limits on server side?
>>
>> Currently we just pull the important branches to "solve" the problem. 
>> But that's just a workaround.
>
> http://selenic.com/hg/rev/510cafe72004  is another workaround for the 
> bad use of Mercurial - it will make the request half as big.
>
> /Mads
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
>
The other workaround - assuming that people do actually commit & push 
reasonable regularly - even if some people don't pull as often as they 
should do - hg log -r -1 to find out your current revision, say it is 
250 then use hg pull -r 251:300, etc., - if that hits the problem then 
try -r 251:275 - so as to pull the changes in manageable chunks.

Also remind people that if the did regular pulls they wouldn't get the 
problem.

BTW I did have the same problem with a hg clone of an SVN repo where 
someone had zipped up a 40 GB binary toolchain and committed it - 
twice!  The workaround there was to pull skipping those two commits and 
the solution was to get the SVN admins to remove the illegal commits.

Gadget/Steve