Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
413 error while pushing the repo
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  4 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
slafs  
View profile  
 More options Apr 23 2012, 5:40 pm
From: slafs <slaf...@gmail.com>
Date: Mon, 23 Apr 2012 14:40:02 -0700 (PDT)
Local: Mon, Apr 23 2012 5:40 pm
Subject: 413 error while pushing the repo

Got an "abort: HTTP Error 413: Request Entity Too Large" while doing

hg push http://....

My configuration involves nginx as a reverse proxy.
It happens near sending the 1900th byte (I think).

Any hints/help or should I post some configs?

Regards

Sławek


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Robin Pellatt  
View profile  
 More options Apr 24 2012, 7:36 am
From: Robin Pellatt <robin.pell...@gmail.com>
Date: Tue, 24 Apr 2012 13:36:49 +0200
Local: Tues, Apr 24 2012 7:36 am
Subject: Re: 413 error while pushing the repo

On 23 April 2012 23:40, slafs <slaf...@gmail.com> wrote:

> Got an "abort: HTTP Error 413: Request Entity Too Large" while doing

> hg push http://....

> My configuration involves nginx as a reverse proxy.
> It happens near sending the 1900th byte (I think).

> Any hints/help or should I post some configs?

> Regards

> Sławek

> Did you mean 1900th KB?  You might want to check "client_max_body_size" in

your  /etc/nginx/nginx.conf, I think the default is only 1MB which is too
low for HG usage.  I set mine to "50m" which is enough for my setup.
Cheers,
Robin.

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Sławek Ehlert  
View profile  
 More options Apr 24 2012, 8:37 am
From: Sławek Ehlert <slaf...@gmail.com>
Date: Tue, 24 Apr 2012 14:37:52 +0200
Local: Tues, Apr 24 2012 8:37 am
Subject: Re: 413 error while pushing the repo

Hi

> Did you mean 1900th KB?

Maybe ;]

>  You might want to check "client_max_body_size" in
> your  /etc/nginx/nginx.conf, I think the default is only 1MB which is
> too low for HG usage.  I set mine to "50m" which is enough for my setup.

I followed the setup on rhodecode documentation and my nginx
configuration looks like this:

==================

upstream rc {
    server 127.0.0.1:5000;
    # add more instances for load balancing
    #server 127.0.0.1:5001;
    #server 127.0.0.1:5002;

}

server {
   listen          80;
   server_name     hg.mga.com.pl;
   access_log      /var/log/nginx/rhodecode.access.log;
   error_log       /var/log/nginx/rhodecode.error.log;

   location /images {
        try_files $uri @static;
   }
   location /css {
        try_files $uri @static;
   }
   location /js {
        try_files $uri @static;
   }

   location / {
        #try_files $uri @static;
        try_files $uri @rhode;
   }

   location @rhode {
        proxy_pass      http://rc;
        include         /etc/nginx/proxy.conf;
   }

   location @static {
        root          
/home/slafs/virtualenvs/rhodecode/lib/python2.6/site-packages/rhodecode/pub lic;
   }

}

==================

and proxy.conf looks like this:

proxy_redirect              off;
proxy_set_header            Host $host;
proxy_set_header            X-Url-Scheme $scheme;
proxy_set_header            X-Host $http_host;
proxy_set_header            X-Real-IP $remote_addr;
proxy_set_header            X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header            Proxy-host $proxy_host;
client_max_body_size        400M;
client_body_buffer_size     128k;
proxy_buffering             off;
proxy_connect_timeout       7200;
proxy_send_timeout          7200;
proxy_read_timeout          7200;
proxy_buffers               8 32k;

===============

So I think that the setting client_max_body_size should be OK.

Regards

Sławek


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
slafs  
View profile  
 More options Apr 24 2012, 5:26 pm
From: slafs <slaf...@gmail.com>
Date: Tue, 24 Apr 2012 14:26:22 -0700 (PDT)
Local: Tues, Apr 24 2012 5:26 pm
Subject: Re: 413 error while pushing the repo

OK. Got it!

including proxy.conf isn't sufficient on the location level. Moved it to
the server level and now it's OK.

This is kind of a documentation issue I think.
http://packages.python.org/RhodeCode/setup.html#nginx-virtual-host-ex...
doesn't seem to work for me on Nginx 0.7.65.

Cheers

W dniu poniedziałek, 23 kwietnia 2012 23:40:02 UTC+2 użytkownik slafs
napisał:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »