On Mon, Sep 19, 2011 at 09:54:16AM +0200, Brane F. Gra??nar wrote:
> On Monday 19 of September 2011 06:18:45 Willy Tarreau wrote:
> >frontend xxx
> >bind 1.2.3.4:80
> >bind /var/run/haproxy/sock-xxx accept-proxy
> >
> > But this requires that the ssl termination supports unix s
On Monday 19 of September 2011 06:18:45 Willy Tarreau wrote:
>frontend xxx
>bind 1.2.3.4:80
>bind /var/run/haproxy/sock-xxx accept-proxy
>
> But this requires that the ssl termination supports unix sockets and I
> believe that stud currently does not.
Just a quick question, Wi
On Sun, Sep 18, 2011 at 11:18:30PM +0200, Sebastien Estienne wrote:
> thanx wily,
>
> last question, in the proxy-protocol.txt it written 'The receiver MUST
> be configured to only receive this protocol and MUST not'
>
> so if i have a line like this in haproxy:
> bind 127.0.0.1:80 accept-proxy
>
thanx wily,
last question, in the proxy-protocol.txt it written 'The receiver MUST
be configured to only receive this protocol and MUST not'
so if i have a line like this in haproxy:
bind 127.0.0.1:80 accept-proxy
only client talking the proxy procol can use the localhost port 80,
standart HTTP
Hello Sebastien,
On Sat, Sep 17, 2011 at 01:27:22PM +0200, Sebastien Estienne wrote:
> Hello,
>
> I'm using stud with haproxy 1.5 in front of a gunicorn/django webapp.
>
> Django looks for X-Forwarded-Protocol=https ou X-Forwarded-Ssl=on
> headers to know if the request is secure or not.
>
> I
Hello,
I'm using stud with haproxy 1.5 in front of a gunicorn/django webapp.
Django looks for X-Forwarded-Protocol=https ou X-Forwarded-Ssl=on
headers to know if the request is secure or not.
I guess it is the job of haproxy to set and forward these headers, but
i don't really know on which cond
6 matches
Mail list logo