Hg Http Error 414 Request-uri Too Large
Contents |
Exception
414 Request-uri Too Large Nginx
during slurp2010-05-20 16:44:51,922 ERROR [InitialPinger8] fisheye.app OneOffPingRequest-doRequest - request-uri too large php Exception during slurp com.cenqua.fisheye.config.ConfigException: Unable to clone remote repository: http://bitbucket.org/mirror/liftweb - [abort: http error 414. the request url is too long HTTP Error 414: Request-URI Too Large] at com.atlassian.fisheye.hg.HgRepositoryEngine.performClone(HgRepositoryEngine.java:127) at com.atlassian.fisheye.dvcs.DvcsRepositoryEngine.cloneRepo(DvcsRepositoryEngine.java:206) at com.atlassian.fisheye.dvcs.DvcsRepositoryEngine.updateClone(DvcsRepositoryEngine.java:180) at com.atlassian.fisheye.dvcs.DvcsRepositoryEngine.doSlurp(DvcsRepositoryEngine.java:79) at com.cenqua.fisheye.rep.RepositoryEngine.slurp(RepositoryEngine.java:353) at com.cenqua.fisheye.rep.ping.OneOffPingRequest.doRequest(OneOffPingRequest.java:28) at com.cenqua.fisheye.rep.ping.PingRequest.process(PingRequest.java:90) at com.cenqua.fisheye.rep.RepositoryHandle.processPingRequests(RepositoryHandle.java:126) at com.cenqua.fisheye.rep.RepositoryHandle.queuePingRequest(RepositoryHandle.java:116) at com.cenqua.fisheye.rep.ping.PingRequest.run(PingRequest.java:57)
How To Fix 414 Request-uri Too Large
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:637) Caused by: com.atlassian.fisheye.plugins.scm.utils.process.ProcessException: Non-zero exit code: 255 at com.atlassian.fisheye.plugins.scm.utils.process.PluggableProcessHandler.complete(PluggableProcessHandler.java:66) at com.atlassian.fisheye.plugins.scm.utils.process.ExternalProcess.finish(ExternalProcess.java:202) at com.atlassian.fisheye.plugins.scm.utils.process.ExternalProcess.execute(ExternalProcess.java:216) at com.atlassian.fisheye.dvcs.client.DvcsContext.executeCommand(DvcsContext.java:183) at com.atlassian.fisheye.dvcs.client.DvcsContext.executeCommand(DvcsContext.java:167) at com.atlassian.fisheye.hg.HgRepositoryEngine.performClone(HgRepositoryEngine.java:114) ... 12 more Cause Mercurial is failing to clone a repository with too many open heads. See this and this page for more details. The list of open heads is causing a server error because of the large URI. Resolution Get the hosting administrator to increase the GET and POST s
a free Git and Mercurial client for Windows. Atlassian SourceTree is a free Git and Mercurial client for Mac. Bitbucket Public Issue Tracker master Issues 414 request-uri too large solution Issues Issue #1895 resolved hg clone/push/pull fails with HTTP Error 414: request-uri too large the requested url's length exceeds the capacity limit for this server. Request-URI Too Large mediawiki created an issue 2010-05-10 We have a large repository with over 300 heads (http://bitbucket.org/mediawiki/root).
The Remote Server Returned An Error 414 Request Uri Too Long
However, due to http://mercurial.selenic.com/bts/issue2126 anyway to clone/pull this repository fails. It is difficult to fix this bug without changing the wire protocol, but maybe the HTTP server URL length https://confluence.atlassian.com/fishkb/unable-to-clone-mercurial-repository-218268760.html limit can be pushed to accommodate large multi-head repositories? hg Comments (6) Jesper Noehr changed status to open I've adjusted the buffer size from 4k to 32k, should have plenty of space to hold the request now. Also, I've adjusted the max POST body from 100M to 2G. Let me know if this has fixed it. 2010-05-10T11:51:41+00:00 mediawiki reporter https://bitbucket.org/site/master/issues/1895/hg-clone-push-pull-fails-with-http-error attached hg Unfortunately, still getting 414. Looks like the HTTP request (including IP and TCP headers) is around 10K, so it should fit the new limit. Attached is a tcpdump of the TCP conversation. 2010-05-10T12:02:15+00:00 Anonymous I get the same thing when I attempt $ hg clone http://bitbucket.org/mirror/liftweb requesting all changes abort: HTTP Error 414: Request-URI Too Large If I do hg clone -r tip http://butbucket.org/mirrow/liftweb it works, but subsequent hg incoming, hg pull etc then get: $ hg pull pulling from http://bitbucket.org/mirror/liftweb searching for changes abort: HTTP Error 500: Internal Server Error I can do hg incoming -r tip but it's not optimal. 2010-05-20T02:49:51+00:00 Jesper Noehr Anon, can you reproduce? 2010-05-21T12:45:57+00:00 Jesper Noehr changed status to resolved 2010-12-14T06:30:13+00:00 Zach Davis staff removed component Removing component: wireprotocol (automated comment) 2014-02-21T19:22:10+00:00 Log in to comment Assignee Jesper Noehr Type bug Priority major Status resolved Component – Votes 0 Watchers 4 Blog Support Plans & pricing Documentation API Site status Version info Terms of service Privacy policy English Git 2.7.4.1.g5468f9e Mercurial 3.6.3 Django 1.7.11 Python 2
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the http://stackoverflow.com/questions/2891574/how-do-i-resolve-a-http-414-request-uri-too-long-error workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs https://groups.google.com/d/topic/mercurial_general/YKOI4-zM9v8 Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; uri too it only takes a minute: Sign up How do I resolve a HTTP 414 “Request URI too long” error? up vote 51 down vote favorite 11 I have developed a PHP web app. I am giving an option to the user to update multiple issues on one go. In doing so, sometimes the user is encountering this error. Is request-uri too large there any way to increase the lenght of URL in apache? php apache http-status-codes share|improve this question edited May 23 '10 at 11:56 John Feminella 175k29272305 asked May 23 '10 at 11:50 JPro 1,74563673 If you're seeing this error on a Windows server and/or in an IIS / ASP.NET app, see question: stackoverflow.com/q/23237538/12484 –Jon Schneider Jan 6 at 16:59 add a comment| 4 Answers 4 active oldest votes up vote 96 down vote accepted Under Apache, the limit is a configurable value, LimitRequestLine. Change this value to something larger than its default of 8190 if you want to support a longer request URI. However, note that if you're actually running into this limit, you are probably abusing GET to begin with. You should use POST to transmit this sort of data -- especially since you even concede that you're using it to update values. If you check the link above, you'll notice that Apache even says "Under normal conditions, the value should not be changed from the default." share|improve this answer edited May 23
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen