Pulls Result in 414: Request URI too large

[Augie Fackler]

On Fri, Dec 29, 2017 at 12:40:46PM -0700, Chuck Lowery wrote:
> I am running into a problem where the Request URI is too large I am unable
> to pull.
>
> Client version is 4.4.2
> Server version is 3.7.3
>
> There are only one or two changesets ahead of me. Pulled earlier (within
> the hour).
>
> We have about ten open named branches.
>
> We use named branches for forking during the creation of new stand-alone
> features and so they created and merged in regularly. The merged in and
> then closed. That is why we only have 10 currently open.
>
> Is there a way to mitigate this problem? Pulling one change at a time
> specifically doesn't seem ideal.

There's always the `[experimental] httppostargs = yes` configuration
option. That will help a *lot*, with the caveat that if you're doing
access control by treating all POST requests as pushes it'll
(probably) break your setup a little.

Maybe explore that next?

>
>
> Charles H. Lowery

> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel