On Wed, Jul 11, 2018 at 8:37 PM Alex Rousskov <
rouss...@measurement-factory.com> wrote:
> On 07/10/2018 11:59 PM, Kedar K wrote:
>
> > I tried to get the request header to store id helper
> > with %>h option for store_id_extras; However, I get a '-'
>
&
On Wed, Jul 11, 2018 at 7:03 PM Hess, Niklas
wrote:
> Hello list,
>
>
>
> I´m setting up a Squid proxy specifically to scan the incoming traffic
> from a cloud platform.
>
> ClamAV should scan the incoming traffic.
>
>
>
> So far so good.
>
>
>
> The cloud uses WebDAV over HTTPS, so I have to SSL
ing from the
data send to store-id helper.
On Wed, Jul 11, 2018 at 3:29 PM Kedar K wrote:
> That was a false alarm; it actually cached only the redirected url and the
> key generated by store-id helper was not used.
>
> On Wed, Jul 11, 2018 at 2:49 PM Kedar K wrote:
>
>&g
That was a false alarm; it actually cached only the redirected url and the
key generated by store-id helper was not used.
On Wed, Jul 11, 2018 at 2:49 PM Kedar K wrote:
> It worked with a combination of store-id helper and url rewriter.
>
> - Kedar
>
> On Wed, Jul 11, 2018 at 1
It worked with a combination of store-id helper and url rewriter.
- Kedar
On Wed, Jul 11, 2018 at 11:42 AM Kedar K wrote:
> additional note:
> I do see both request and response header in access.log though.
>
> On Wed, Jul 11, 2018 at 11:29 AM Kedar K wrote:
>
>> Hi,
additional note:
I do see both request and response header in access.log though.
On Wed, Jul 11, 2018 at 11:29 AM Kedar K wrote:
> Hi,
> I tried to get the request header to store id helper
> with %>h option for store_id_extras; However, I get a '-' (and the default
>
Hi,
I tried to get the request header to store id helper
with %>h option for store_id_extras; However, I get a '-' (and the default
k-v pairs intact)
Is this expected behaviour? Wouldn't request header be available before
sending a query to store-id helper?
My use case was to pass custom fields
d then to origin server. However, with https header forgery kicks
in and tls is terminated.
- Kedar
On Mon, Jun 18, 2018 at 9:44 AM Amos Jeffries wrote:
> On 18/06/18 02:08, Kedar K wrote:
> > Hello,
> >
> > I am hitting this issue when running squid in a docker with ssl parent
&
Hello,
I am hitting this issue when running squid in a docker with ssl parent
cache_peer.
Host header forgery detected on local=11 72.19.0.2:443 remote=
172.19.0.1:44522 FD 15 flags=33 (local IP does not match any domain IP)
The host ip of the docker would not resolve to a domain. How to
work-a
