Support for HTTPS backends was added in Pound 2.5c.

You configure in a backend group by using the HTTPS Directive.  From the Pound 
manual page:

BackEnd
       A back-end is a definition of a single back-end server Pound will use to 
reply to incoming requests.  All configuration directives enclosed between 
BackEnd and End
       are specific to a single service. The following directives are available:

       Address address
              The address that Pound will connect to. This can be a numeric IP 
address, or a symbolic host name that must be resolvable at run-time. If the 
name cannot be
              resolved to a valid address, Pound will assume that it represents 
the path for a Unix-domain socket. This is a mandatory parameter.

       Port port
              The port number that Pound will connect to. This is a mandatory 
parameter for non Unix-domain back-ends.

       HTTPS [ "cert" ]
              The back-end is using HTTPS. If the optional parameter cert is 
specified, Pound will present this certificate to the back-end.

       Priority val
              The  priority  of  this  back-end (between 1 and 9, 5 is 
default). Higher priority back-ends will be used more often than lower priority 
ones, so you should
              define higher priorities for more capable servers.

       TimeOut val
              Override the global TimeOut value.

       ConnTO val
              Override the global ConnTO value.

       HAport [ address ] port
              A port (and optional address) to be used for server function 
checks. See below the "High Availability" section for a more detailed  
discussion.  By  default
              Pound  uses the same address as the back-end server, but you may 
use a separate address if you wish. This directive applies only to non 
Unix-domain servers.


Joe


> -----Original Message-----
> From: nelson pereira [mailto:[email protected]]
> Sent: Sunday, January 09, 2011 9:51 PM
> To: [email protected]
> Subject: Re: [Pound Mailing List] About https
>
> does pound do https to https backend?
>
> I think this is something proxmox does not actualy do.. am i wrong?
>
> Nelson
>
> On Jan 9, 2011, at 5:33 PM, Dave Steinberg wrote:
>
> > On 1/9/2011 5:25 PM, Nelson Pereira wrote:
> >> done that, and the service looks like this:
> >>
> >>         Service
> >>                 HeadRequire "Host:.*proxmox.mydomain.com.*"
> >>                 BackEnd
> >>                         Address 192.168.1.10
> >>                         Port    443
> >>                 End
> >>         End
> >>
> >> Yet I keep getting the logs in syslog:
> >> can't read header
> >> e500 response error read from 192.168.1.10:443/GET / HTTP/1.1:
> Success
> >> (0.001 secs)
> >>
> >> and then i get a page cannot be displayed.
> >
> > Try adding "HTTPS" to the backend directive.  I'm not 100% sure of
> the syntax there, I think its literally a bareword as in:
> >
> > BackEnd
> >     Address 192...
> >     Port 443
> >     HTTPS
> > End
> >
> > That will tell pound to talk https to the backend.  I don't use that
> myself so I can't advise precisely how it should look, but play around
> with it or maybe check the archives to see if there are examples.
> >
> > Regards,
> > --
> > Dave Steinberg
> > http://www.geekisp.com/
> > http://www.steinbergcomputing.com/
> > http://www.redterror.net/
> >
> > --
> > To unsubscribe send an email with subject unsubscribe to
> [email protected].
> > Please contact [email protected] for questions.
>
>
> --
> To unsubscribe send an email with subject unsubscribe to
> [email protected].
> Please contact [email protected] for questions.

--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.

Reply via email to