Why dont you use redirect on pound under listen http and point it to HTTPS.
ListenHTTP
         Address 192.168.0.10
         Port    80
         Service
         Redirect "https://myserver.to.pound/subdir";
         End
End


On Fri, Dec 12, 2008 at 10:38 AM, Shamunda <[email protected]> wrote:

> Hello -
>
> After going through much of the archives for SSL i was finally able to get
> something to work, I think :)
>
> Howerver i'm a bit confused as to how it's supposed to work.
>
> Here's what i see happening and what i think is happening:
>
> I type https://myserver.to.pound/subdir, pound forwards the request --->
> http://my.backend.servers/subdir.
>
> However the url changes in my web browser to -
> http://myserver.to.pound/subdir.  Shouldn't everything be returned back to
> me as HTTPS?
>
> I'm sure i have something really screwed up so I provided my config.  I
> could use any and all help, thanks again.
>
>
> --------------------------
> Here's my config:
>
> ## Minimal pound.cfg
>
> ## Global Op
>
> User    "www-data"
> Group   "www-data"
> #RootJail       "/chroot/pound"
>
> ## Logging Level
> ##      0       no logging
> ##      1       normal
> ##      2       extended
> ##      3       Apache-style
> LogLevel 1
>
> ## Check backend every x secs:
> Alive   2
>
> ## User hardware Acceleration
> ## SSLEngine    "<hw>"
>
> ListenHTTPS
>   Address 192.168.0.10
>   Port    443
>   Cert    "/etc/ssl/server.pem"
>   Service
>      BackEnd
>        Address 192.168.0.100
>        Port 80
>      End
>      BackEnd
>        Address 192.168.0.200
>        Port 80
>      End
>   End
> End
>
> ***** Email confidentiality notice *****
>
> 12/12/2008
>
> This message is private and confidential.  If you have recieved this
> message in error, please notify us and remove it from your system.
>
>
>
>
> --
> 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