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

[Daniel Siepmann]

Our Version on the Server is 2.2.2.
On client side it depends on the local machine. In my own case it's 3.0.1
but there are still older versions in use.

I tried some sniffer tools to get the generated URL and understand what's
causing the long URL. But I couldn't fetch the URL ...
So what's the Problem? The heads, Branches, even closed branches?


On Wed, Aug 27, 2014 at 5:50 AM, Matt Mackall <mpm at selenic.com> wrote:

> On Tue, 2014-08-26 at 13:44 +0200, 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.
> >
> > I'm looking forward your help and explanations.
>
> Let's start with the single most important piece of information:
>
> What version of Mercurial are you using?
>
> --
> Mathematics is the supreme nostalgia of our time.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20140829/c40c92df/attachment-0002.html>