Hello Robert,
thanks a lot for your quick response.
> Sorry, but for the moment poundctl and emergency BEs are not supported.
> We may add them in a future version.
I will be patient :)
> If you really need these features I suggest you stay with the 2.x
series.
Really 'needed' is an easy way
Hello Robert,
migrating some webfrontends from Debian 9 to Debian 11 urges us to use pound
3.x instead of 2.x!
We used to monitor our pound instances and disable/enable backends in pound 2.x
via poundctl.
Also the approach of emergency-backends seems to be unimplemented in 3.x?
Is the only
my experience if redirects from backend dont work properly, is to tune
with the "RewriteLocation" option. for example add
RewriteLocation 2
to your listener...
good luck and cheers.ivo
On 06/19/2013 10:45 AM, Alan McGinlay wrote:
Hmm, I'm not awesome at spotting that kind of issue (sounds like
hi mark
i add this to the listenHTTPS
AddHeader "IS_SSL: SSL"
so http-requests on apache side that entered as https to pound got this
header.
then i do something like this on apache:
RewriteEngine On
RewriteCond %{HTTP:IS_SSL} !^SSL$
RewriteRule ^(.*) https://site.com/$1 [
hi list
this one has taken me 2 days to fix, so i hope i can help someone else
with this post:
after upgrades i've seen a constant 5s lag on the proxy when the backend
sends a 302. with tcpdump i've seen pound waiting 5s before sending the
302 to me. at the end it was an glibc update that no