Hello,

can nobody help me?

any help would be appreciated

kind regards

Philipp Michels


-- 
Dipl.-Inf. Philipp Michels
Rechenzentrum Universitaet Freiburg
Hermann-Herder-Str. 10, 79104 Freiburg
Tel: 0761/203-4664, FAX: 0761/203-4643
E-Mail: michels(at)rz.uni-freiburg.de

PGP-Key: http://omnibus.ruf.uni-freiburg.de/~michels/pubkey.asc
PGP-Fingerprint: 80DE 5B0A E847 BC54 27B0 CBE8 33FF 3B6B 8900 9913


Philipp Michels schrieb:
> Hello,
> 
> i read the archive of the pound maillinglist but did not find a answer
> which solves my problem.
> 
> We have running a zope server and use pound to do load balancing. At the
> moment all requests to http://<zope_server>/manage will be blocked from
> the first pound instance with the line:
> 
> UrlGroup ".*/manage$"
> EndGroup
> 
> I would like to setup a configuration so that all manage requests will
> redirected to the 2nd pound instance which handels https requests. I
> tried it that way:
> 
> request http://<zope_server>/manage --> 1st pound (redirect) --> 2nd
> pound --> response https://<zope_server>/manage
> 
> 1st pound instance:
> 
> ## Redirect Zope-Management-Interface to HTTPS pound backend
> Service
>   URL ".*/manage$"
>   BackEnd
>     Address 132.230.7.46 # 2nd pound instance
>     Port    443
>   End
> End
> 
> 2nd pound instance:
> 
> [...]
> Client		300
> AddHeader	"HTTPS: ON"
> RewriteLocation 2
> 
> Service
>   URL ".*/manage$"
>   BackEnd
>     Address 132.230.7.46
>     Port    7081  # port for zope
>   End
> End
> 
> 
> this configuration does not work i get the following error:
> 
> pound: response error read from 132.230.7.46:443: Success
> 
> I tried already the redirect option on 1st pound instance. This works
> but i have to do the HTTP Authentification two times. First for
> http://<zope_server> and second for https://<zope_server>.
> 
> Any suggestions?
> 
> kind regards
> 
> Philipp Michels
> 

Philipp Michels wrote:
> Hello,
> can nobody help me?
> any help would be appreciated
> kind regards
> Philipp Michels


What it looks like you are attempting to do is forward on the HTTP
request to an HTTPS server, correct?  Pound does not have client HTTPS
capabilities.  Pound can only receive HTTPS requests, unwrap them, and
then forward on HTTP requests.

If you would like to do a redirect back to the client, and have the
client directly accesses the HTTPS server, then yes, Pound can do this.

Kenneth

Dave Steinberg wrote:
> Leonard Bethea wrote:
>>
>> I was able to get the redirect to work. I tweaked your code a little and
>> added the header. If it's a SSL cert then everything works now. If the
>> header is not https then I redirect to the secure link; however, the
>> redirect does not pass the form information. I was wondering if this was
>> because of mod_rewrite or pound?
> 
> Neither - if your application is submitting a form to a HTTP url and you
> expect to receive variables, the redirector is going to need to turn the
> POST variables into the query string of the redirect URL (thereby
> turning them into "GET variables".  In this case you're looking at a
> custom redirector rather than using mod_rewrite for it - at least if I'm
> understanding you correctly.
> 
> Naturally I'd recommend avoiding this if possible, as any large forms
> won't be too happy.

Either "301 Moved Permanently"
(http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.2) or
"307 Temporary Redirect"
(http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.8) are
the HTTP responses to redirect a POST to a different URL without the
user agent changing it to a GET.

Not sure how well redirecting POSTs supported by browsers though - read
the notes for status codes 301, 302, 303 and 307, and do careful
testing! http://www.browsercam.com/ might help; I'd be interested in
knowing whether you are successful or not!

Regards,

Russ

-- 
Russell Odom
Technical Director, Zolv

Eagles may soar, but weasels aren't sucked into jet engines.

I'll read the information but I'm not going to redirect Post pages. I'm
going to write an error page and redirect to the error page if it's coming
through http. That seemed like the fastest way to get this accomplished. 

I'm still redirecting non Post pages though.

Leonard

-----Original Message-----
From: Russell Odom [mailto:listsignups(at)zolv.com] 
Sent: Thursday, August 02, 2007 9:25 AM
To: pound(at)apsis.ch
Subject: Re: [Pound Mailing List] mod_rewrite

Dave Steinberg wrote:
> Leonard Bethea wrote:
>>
>> I was able to get the redirect to work. I tweaked your code a little and
>> added the header. If it's a SSL cert then everything works now. If the
>> header is not https then I redirect to the secure link; however, the
>> redirect does not pass the form information. I was wondering if this was
>> because of mod_rewrite or pound?
> 
> Neither - if your application is submitting a form to a HTTP url and you
> expect to receive variables, the redirector is going to need to turn the
> POST variables into the query string of the redirect URL (thereby
> turning them into "GET variables".  In this case you're looking at a
> custom redirector rather than using mod_rewrite for it - at least if I'm
> understanding you correctly.
> 
> Naturally I'd recommend avoiding this if possible, as any large forms
> won't be too happy.

Either "301 Moved Permanently"
(http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.2) or
"307 Temporary Redirect"
(http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.8) are
the HTTP responses to redirect a POST to a different URL without the
user agent changing it to a GET.

Not sure how well redirecting POSTs supported by browsers though - read
the notes for status codes 301, 302, 303 and 307, and do careful
testing! http://www.browsercam.com/ might help; I'd be interested in
knowing whether you are successful or not!

Regards,

Russ

-- 
Russell Odom
Technical Director, Zolv

Eagles may soar, but weasels aren't sucked into jet engines.

--
To unsubscribe send an email with subject unsubscribe to pound(at)apsis.ch.
Please contact roseg(at)apsis.ch for questions.

On Tue, 2007-07-31 at 03:02 +0200, Aigner wrote:
> Just wanted to test Dynamic Scaling with latest V2.4c (compiled "./configure
> --with-log=LOG_LOCAL7 --enable-dynscale"), but pound
> daemon will not start. Instead it states :
> "unknown directive "DynScale^I1" - aborted"
>  
> I globally set :
> DynScale    1
>  
> If I remove the line, pound will start again.
>  
> Any ideas ? 

It sounds very much like you are using an older version. 2.4c does NOT
use the --enable-dynscale in the autoconf, but only the config file
directive. Check your version.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904

On Tue, 2007-07-31 at 17:11 +0100, Anthony Underwood wrote:
> Hi All,
> 
> Is it possible to perform a case sensitive match within a URL directive? I
had a look through the documentation and could see no mention of this.

Thanks for pointing that out - it will be fixed in the next release.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904

On Wed, 2007-07-25 at 16:11 +0200, Gergely CZUCZY wrote:
> hello,
> 
> I've started testing pound, and i'm stressing it with around
> 100-128 simultaneous connections from ab (apache benchmark). I
> don't really know how many request/sec is that, because I've
> disabled the normal logging to see the error logs.
> 
> I'm recieving hordes of broken pipes from pound. I've got
> hourly log rotating, so the last hour's results are:
> # bzgrep 'pound: error copy server cont: Broken pipe' messages.0.bz2 | wc -l
>     5718
> 
> # for i in `bzgrep -A 2 'pound: error copy server cont: Broken pipe'
messages.0.bz2  | grep 'last message repeated' | awk '{print $8}'`; do
sum=$(($sum+$i)); done
> # echo $sum
> 118046
> 
> That's quite much, in my opinion.
> 
> I'm running it on a FreeBSD 6.2-p6, with libthr instead of the default
libpthread.
> 
> How can this issue be fixed?

It's quite inoffensive: it really means that ab closed a connection
before receiving the full response. In practice it doesn't happen that
much, though it can't be avoided completely.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904

> It sounds very much like you are using an older version. 2.4c 
> does NOT use the --enable-dynscale in the autoconf, but only 
> the config file directive. Check your version.
Also if compiling with only "--with-log=LOG_LOCAL7" I get the same error.

Calling "pound -V" gives me 2.4c as version information.

--
Oliver Aigner

> -----Original Message-----
> From: Robert Segall [mailto:roseg(at)apsis.ch] 
> Sent: Thursday, August 02, 2007 6:25 PM
> To: pound(at)apsis.ch
> Subject: Re: [Pound Mailing List] DynScale not working
> 
> On Tue, 2007-07-31 at 03:02 +0200, Aigner wrote:
> > Just wanted to test Dynamic Scaling with latest V2.4c (compiled 
> > "./configure
> > --with-log=LOG_LOCAL7 --enable-dynscale"), but pound daemon 
> will not 
> > start. Instead it states :
> > "unknown directive "DynScale^I1" - aborted"
> >  
> > I globally set :
> > DynScale    1
> >  
> > If I remove the line, pound will start again.
> >  
> > Any ideas ? 
> 
> It sounds very much like you are using an older version. 2.4c 
> does NOT use the --enable-dynscale in the autoconf, but only 
> the config file directive. Check your version.
> --
> Robert Segall
> Apsis GmbH
> Postfach, Uetikon am See, CH-8707
> Tel: +41-44-920 4904
> 
> 
> --
> To unsubscribe send an email with subject unsubscribe to 
> pound(at)apsis.ch.
> Please contact roseg(at)apsis.ch for questions.

Well, you were fully right.
init.d script called older version 2.0.6 in /usr/sbin. But the new version
resides in /usr/local/sbin.

The new version works like a charm. It is really a software master-piece :-)
If you are into Zope and need an high performance and reliable front-end,
then choose pound !

Thanks,
Oliver Aigner

> -----Original Message-----
> From: Aigner [mailto:VooDoo(at)ganjacru.de] 
> Sent: Friday, August 03, 2007 12:51 AM
> To: pound(at)apsis.ch
> Subject: RE: [Pound Mailing List] DynScale not working
> 
> > It sounds very much like you are using an older version. 
> 2.4c does NOT 
> > use the --enable-dynscale in the autoconf, but only the config file 
> > directive. Check your version.
> Also if compiling with only "--with-log=LOG_LOCAL7" I get the 
> same error.
> 
> Calling "pound -V" gives me 2.4c as version information.
> 
> --
> Oliver Aigner
> 
> > -----Original Message-----
> > From: Robert Segall [mailto:roseg(at)apsis.ch]
> > Sent: Thursday, August 02, 2007 6:25 PM
> > To: pound(at)apsis.ch
> > Subject: Re: [Pound Mailing List] DynScale not working
> > 
> > On Tue, 2007-07-31 at 03:02 +0200, Aigner wrote:
> > > Just wanted to test Dynamic Scaling with latest V2.4c (compiled 
> > > "./configure
> > > --with-log=LOG_LOCAL7 --enable-dynscale"), but pound daemon
> > will not
> > > start. Instead it states :
> > > "unknown directive "DynScale^I1" - aborted"
> > >  
> > > I globally set :
> > > DynScale    1
> > >  
> > > If I remove the line, pound will start again.
> > >  
> > > Any ideas ? 
> > 
> > It sounds very much like you are using an older version. 
> 2.4c does NOT 
> > use the --enable-dynscale in the autoconf, but only the config file 
> > directive. Check your version.
> > --
> > Robert Segall
> > Apsis GmbH
> > Postfach, Uetikon am See, CH-8707
> > Tel: +41-44-920 4904
> > 
> > 
> > --
> > To unsubscribe send an email with subject unsubscribe to 
> > pound(at)apsis.ch.
> > Please contact roseg(at)apsis.ch for questions.
> 
> 
> --
> To unsubscribe send an email with subject unsubscribe to 
> pound(at)apsis.ch.
> Please contact roseg(at)apsis.ch for questions.