found out yesterday that there is no backward
compatibility since a typical redirection URL is
www.example.com/foo.cgi?category=adulturl=http://www.example.com/foo/bar
and Squid 3.4 has a parser that splits tokens at '=' and then complains
that it does not understand the answer of the URL redirector
versions of Squid.
Despite Amos' belief, I found out yesterday that there is no backward
compatibility since a typical redirection URL is
www.example.com/foo.cgi?category=adulturl=http://www.example.com/foo/bar
and Squid 3.4 has a parser that splits tokens at '=' and then complains
]
Envoyé : mercredi 14 novembre 2012 19:34
À : Vincent Miszczak
Cc : squid-dev@squid-cache.org
Objet : Re: Squid HEAD : intercept SSLBump server first + out of Squid box NAT
redirection
On 11/14/2012 11:17 AM, Vincent Miszczak wrote:
I'd like to know how Squid resolves the remote host when
On 11/15/2012 10:53 AM, Vincent Miszczak wrote:
Hi,
Thank you for your answer.
I understand I cannot redirect SSL web traffic to intercepting Squid using NAT
from another box, as Squid won't be able to figure out the destination address,
right ?
Vincent
yes, but you can use --set-mark with
On 15/11/2012 9:53 p.m., Vincent Miszczak wrote:
Hi,
Thank you for your answer.
I understand I cannot redirect SSL web traffic to intercepting Squid using NAT
from another box, as Squid won't be able to figure out the destination address,
right ?
Yes. That is one of the side effects of NAT
Hi guys,
I'm testing this feature, working like it should at the moment, great feature :)
For now, I've been testing with an inline Linux server using iptables
redirection. Both Netfilter REDIRECT and DNAT targets make this configuration
work.
My production setup won't have the Squid box
On 11/14/2012 11:17 AM, Vincent Miszczak wrote:
I’d like to know how Squid resolves the remote host when handling an
intercepted server-first bumped connection, so I’ll be able to setup my
network accordingly.
Using the destination address of the intercepted TCP connection, Squid
securely
Easiest: Implement your filter using ICAP, and in your ICAP server agent
buffer the response until you find it's OK. If not OK replace the
response with your blocking page..
Doing this within Squid is a bit hairy..
Regards
Henrik
while finding on ICAP servers i came accross this : there
reference
implementation from NetApp, linked from the i-cap.org site. You can
customize them. plugIf you want more support and less work, The
Measurement Factory builds ICAP servers to suit and also provides
Traffic Spicer, the bare-bones ICAP server where you can plug in your
redirection logic./plug
FWIW
2.6 stable 6 and i cudnt find that fucntion in the source
code.. is it a part of the later releases?
also please if any one can tell us...
what would be the easiest way to start the redirection to our server's custom
page
which says page blocked as in what function is responsible for starting
been doing to
2.6stable9+.
what would be the easiest way to start the redirection to our server's
custom page
which says page blocked as in what function is responsible for starting
the redirection to another page and the data structures also responsible
for
holding the current URL so that we
On Wed, 21 Jul 2004, Ram Kumar Gandhapuneni wrote:
I am a novice squid developer. I am trying to make modifications to
the code in the client_side to do the redirection based on http header of
the requests.
Please describe a little more in detail what it is you want to do (the
purpose
Hi,
I am a novice squid developer. I am trying to make modifications to
the code in the client_side to do the redirection based on http header of
the requests. I saw a thread with suggestions to start at redirectStart.
It would be great if anybody can give me more elaborate description
an open case with cisco about this).
So i tried implementing wccpv2. to my dismay the cisco 3550 does not support wccpv2
with GRE packet redirection. it must use Layer 2 redirection. so when i run squid
with the wccpv2 i get the following errors on the cisco 3550 (off course i change both
configs
On Tue, 11 Nov 2003, John El-Rassi wrote:
So i tried implementing wccpv2. to my dismay the cisco 3550 does not
support wccpv2 with GRE packet redirection.
No problem in theory. L2 redirection just makes life a whole lot easier as
you don't need any GRE module, just normal interception rules
with. ( menaing if i type in the web browser the IP address of the
cisco switch. the web managment interface of the router). when i do that i see the
redirection counter on the cisco incrementing and the access.log on squid showing the
request and query.
However if i do from the same client any
to the net. it however redirects traffic if the destination ip
of the web request was any IP that the cisco is configured with. (
menaing if i type in the web browser the IP address of the cisco switch.
the web managment interface of the router). when i do that i see the
redirection counter
the cisco 3550 does not support wccpv2
with GRE packet redirection. it must use Layer 2 redirection. so when i run squid
with the wccpv2 i get the following errors on the cisco 3550 (off course i change
both configs on cisco and squid wccp2_router and ip wccp version 2)
17:19:43: WCCP
18 matches
Mail list logo
