On Wed, Sep 18, 2019 at 7:11 AM Amos Jeffries wrote:
>
>
> All these *_port things are a red herring. The initial problem was
> connections to the origin server using HTTPS.
>
> Connections to originserver peer do not send URL scheme, and use the
> settings on the cache_peer directive as the proto
On Tue, Sep 17, 2019 at 4:07 PM Alex Rousskov
wrote:
>
> On 9/17/19 2:07 PM, Sam Holden wrote:
>
> > https_port 4277 accel ... protocol=http
>
> > sees port 4227 act as an http port (no ssl)
>
> Assuming you meant "4277" when you said "4227"
ame effect).
Is there an option to have squid make HTTP requests on behalf of HTTPS
requests from clients?
--
Sam Holden
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
