From: "ArcosCom Linux User" <linux@arcoscom.com>
To: netfilter@vger.kernel.org
Subject: Re: Https website is not accessible once transparent proxy is set up
Date: Tue, 16 Sep 2008 13:50:23 +0200 (CEST) [thread overview]
Message-ID: <fb6debad85eb3106cd197c989db6027c.squirrel@www.arcoscom.com> (raw)
In-Reply-To: <48CF9644.7010504@oracle.com>
El Mar, 16 de Septiembre de 2008, 13:19, John Haxby escribió:
> ArcosCom Linux User wrote:
>> Read about HTTP transparent proxy.
>>
>> The HTTPS can't be transparently proxied (as I now) for yet.
>>
>
> Well, not by squid, but the connection can be transparently proxied. I
> have a tiny transparent proxy that redirects all connections to any port
> outside an intranet to a connection through an HTTP CONNECT request.
>
As I now (and have working some HTTP proxyes with squid+iptables), the
problem are the requests.
Well, when you do a REDIRECT from 80 to 3128 (for squid), the squid must
know that it is working in transparent mode to process correctly the HTTP
requests, because they aren't directly for the proxy.
If you use the same theory for any other protocol, the "proxy" must know
how to process correctly these type of connections.
What "tiny transparent proxy" are you using? Perhaps, anybody could help
you in any trick with it!!.
> jch
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Regards
next prev parent reply other threads:[~2008-09-16 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 6:49 Https website is not accessible once transparent proxy is set up Sam Chan
2008-09-16 11:03 ` ArcosCom Linux User
2008-09-16 11:19 ` John Haxby
2008-09-16 11:50 ` ArcosCom Linux User [this message]
2008-09-16 13:50 ` John Haxby
2008-09-16 18:01 ` Vimal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb6debad85eb3106cd197c989db6027c.squirrel@www.arcoscom.com \
--to=linux@arcoscom.com \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox