On 4/04/2016 4:18 p.m., Jok Thuau wrote:
> I'm attempting to build a transparent proxy (policy based routing on
> firewall to squid proxy) with the following behavior:
>
> 1) proxies http traffic for a given set of domains, provide an message
> otherwise such "domain not allowed" or similar
> 2)
I'm attempting to build a transparent proxy (policy based routing on
firewall to squid proxy) with the following behavior:
1) proxies http traffic for a given set of domains, provide an message
otherwise such "domain not allowed" or similar
2) proxies https traffic for a given set of domains
On 4/04/2016 4:22 a.m., Brendan Kearney wrote:
> with fedora 24 being released in a couple months, haproxy v1.6.x will be
> available, and the ability to easily intercept HTTP traffic will be in
> the version (see the set-uri directive). with v1.6 i will be able to
> rewrite the URL, so that
On 4/04/2016 12:46 a.m., Sreenath BH wrote:
> Hi Amos,
>
> Thanks for the information.
> We are not using any helpers in the first squid, no ICAP/rCAP as well.
Aha. That will be the problem then. With no helper to make Squid aware
that there is anything special about the WWW-Auth headers they
I am unsure what you want to achieve.
Do you want to cache one specific url or a set of urls?
Also are you targeting one host\url and\or also one client or more?
It will depend on the level of control that you have on the client side.
If you are in a position to Intercept all the traffic it
with fedora 24 being released in a couple months, haproxy v1.6.x will be
available, and the ability to easily intercept HTTP traffic will be in
the version (see the set-uri directive). with v1.6 i will be able to
rewrite the URL, so that squid can process the request properly. my
problem is
