Tory M Blue wrote:
I was wondering if there was a way for Squid to pass on some basic
information to the server citing that the original request was Secure,
so that the backend server will respond correctly.
Right now Squid takes and handles the SSL, passes back to the server
via standard http a
On Thu, May 1, 2008 at 2:02 AM, Amos Jeffries <[EMAIL PROTECTED]> wrote:
>
> You could make a second peer connection using HTTPS between squid and the
> back-end server and ACL the traffic so that only requests coming in via SSL
> are sent over that link. Leaving non-HTTPS incoming going over the
. mywebsite.com
cache_peer_access httpsWeb allow ourWebSite
> -Original Message-
> From: Tory M Blue [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 01, 2008 11:21 AM
> To: squid-users@squid-cache.org
> Subject: Re: [squid-users] SSL Accel - Reverse Proxy
>
> On Thu, M
Tory M Blue wrote:
On Thu, May 1, 2008 at 2:02 AM, Amos Jeffries <[EMAIL PROTECTED]> wrote:
You could make a second peer connection using HTTPS between squid and the
back-end server and ACL the traffic so that only requests coming in via SSL
are sent over that link. Leaving non-HTTPS incoming g
On Fri, May 2, 2008 at 5:25 AM, Amos Jeffries <[EMAIL PROTECTED]> wrote:
>
> You made the situation clear. I mentioned the only reasonably easy
> solution.
> If you didn't understand me, Keith M Richad provided you with the exact
> squid.conf settings I was talking about before.
Obviously i ha
> Sent: Friday, May 02, 2008 7:26 AM
> To: Tory M Blue
> Cc: squid-users@squid-cache.org
> Subject: Re: [squid-users] SSL Accel - Reverse Proxy
>
> Tory M Blue wrote:
> > On Thu, May 1, 2008 at 2:02 AM, Amos Jeffries <[EMAIL PROTECTED]>
> wrote:
> >> You
On ons, 2008-04-30 at 11:10 -0700, Tory M Blue wrote:
> I was wondering if there was a way for Squid to pass on some basic
> information to the server citing that the original request was Secure,
> so that the backend server will respond correctly.
Yes. See the front-end-https cache_peer option.
Tory M Blue wrote:
On Fri, May 2, 2008 at 5:25 AM, Amos Jeffries <[EMAIL PROTECTED]> wrote:
You made the situation clear. I mentioned the only reasonably easy
solution.
If you didn't understand me, Keith M Richad provided you with the exact
squid.conf settings I was talking about before.
O
Amos Jeffries wrote:
Tory M Blue wrote:
On Fri, May 2, 2008 at 5:25 AM, Amos Jeffries <[EMAIL PROTECTED]>
wrote:
You made the situation clear. I mentioned the only reasonably easy
solution.
If you didn't understand me, Keith M Richad provided you with the exact
squid.conf settings I was tal
On Fri, May 2, 2008 at 6:17 PM, Henrik Nordstrom
<[EMAIL PROTECTED]> wrote:
> On ons, 2008-04-30 at 11:10 -0700, Tory M Blue wrote:
> > I was wondering if there was a way for Squid to pass on some basic
> > information to the server citing that the original request was Secure,
> > so that the ba
On Mon, May 5, 2008 at 9:23 AM, Tory M Blue <[EMAIL PROTECTED]> wrote:
>
> On Fri, May 2, 2008 at 6:17 PM, Henrik Nordstrom
> <[EMAIL PROTECTED]> wrote:
> > On ons, 2008-04-30 at 11:10 -0700, Tory M Blue wrote:
> > > I was wondering if there was a way for Squid to pass on some basic
> > > inf
On mån, 2008-05-05 at 09:23 -0700, Tory M Blue wrote:
> Either I have this implemented wrong (more likely). Or the directive
> is not quite right.
Quote from the documentation:
front-end-https[=on|auto]
use front-end-https to enable the "Front-End-Https: On"
The authorative documentaiton is squid.conf.default, or the copy found
online on squid-cache.org.
http://www.squid-cache.org/Versions/v2/2.6/cfgman/cache_peer.html
Regards
Henrik
On mån, 2008-05-05 at 11:25 -0700, Tory M Blue wrote:
> visolve documentation
>
> front-end-https
>
>
>to
13 matches
Mail list logo
