[prev in list] [next in list] [prev in thread] [next in thread] 

List:       uwsgi
Subject:    [uWSGI] Mercurial push only works with nginx, hangs with Cherokee
From:       njriley () illinois ! edu (Nicholas Riley)
Date:       2011-07-19 15:32:01
Message-ID: njriley-7E7F3F.11320119072011 () news ! gmane ! org
[Download RAW message or body]

In article <96613ee70f229799d46f0105bb51f03e.squirrel at manage.unbit.it>,
 "Roberto De Ioris" <roberto at unbit.it> wrote:

> Does "GET request" for mercurial works in Cherokee ?

Yes, I can do GET requests of arbitrary sizes (hundreds of MB).

Here are logs from the client and server side for Cherokee and Nginx 
with uWSGI:

Cherokee:

Client -

pushing to https://<server>/hg/oncall/Application/test/
using https://<server>/hg/oncall/Application/test/
sending capabilities command
<server> certificate successfully verified
query 1; heads
sending batch command
searching for changes
taking quick initial sample
searching: 2 queries                                                            
query 2; still undecided: 3343, sample size is: 19                              
sending known command                                                           
sampling from both directions                                                   
searching: 3 queries                                                            
query 3; still undecided: 453, sample size is: 200                              
sending known command 
                                                          
Server -

10.251.67.170 - - [19/Jul/2011:11:29:21 -0400] "GET 
/hg/oncall/Application/test/?cmd=capabilities HTTP/1.1" 200 291 "-" 
"mercurial/proto-1.0"
10.251.67.170 - - [19/Jul/2011:11:29:24 -0400] "GET 
/hg/oncall/Application/test/?cmd=batch HTTP/1.1" 200 203 "-" 
"mercurial/proto-1.0"
10.251.67.170 - - [19/Jul/2011:11:29:24 -0400] "GET 
/hg/oncall/Application/test/?cmd=known HTTP/1.1" 200 179 "-" 
"mercurial/proto-1.0"

nginx:

Client -

pushing to http://<server>:8000/hg/oncall/Application/test/
using http://<server>:8000/hg/oncall/Application/test/
sending capabilities command
query 1; heads
sending batch command
searching for changes
taking quick initial sample
searching: 2 queries                                                            
query 2; still undecided: 3343, sample size is: 19                              
sending known command                                                           
sampling from both directions                                                   
searching: 3 queries                                                            
query 3; still undecided: 453, sample size is: 200                              
sending known command                                                           
3 total queries                                                                 
3344 changesets found
list of changesets:
26304fcbf5116da0d551027766cb2e0f2d526241
[...]

Server -

10.251.67.170 - - [19/Jul/2011:11:27:56 -0400] "GET 
/hg/oncall/Application/test/?cmd=capabilities HTTP/1.1" 200 130 "-" 
"mercurial/proto-1.0"
10.251.67.170 - - [19/Jul/2011:11:27:58 -0400] "GET 
/hg/oncall/Application/test/?cmd=batch HTTP/1.1" 200 43 "-" 
"mercurial/proto-1.0"
10.251.67.170 - - [19/Jul/2011:11:27:58 -0400] "GET 
/hg/oncall/Application/test/?cmd=known HTTP/1.1" 200 19 "-" 
"mercurial/proto-1.0"
10.251.67.170 - - [19/Jul/2011:11:27:58 -0400] "GET 
/hg/oncall/Application/test/?cmd=known HTTP/1.1" 200 200 "-" 
"mercurial/proto-1.0"

So it looks like the last "known" command is the first request that's 
failing.
-- 
Nicholas Riley <njriley at illinois.edu>


[prev in list] [next in list] [prev in thread] [next in thread]