If you want, please support this topic in the bug-report
http://lists.squid-cache.org/pipermail/squid-users/2018-July/018743.html
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
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 '-'
>
> > store_id_extras "%>h %>a/%>A %un %>rm
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 '-'
> store_id_extras "%>h %>a/%>A %un %>rm myip=%la myport=%lp"
> Is this expected behaviour?
No, it is not expected. Consider filing a bug
With following config to access request header;
store_id_extras "%>h %>a/%>A %un %>rm myip=%la myport=%lp"
the store_id_extras does not seem to forward header info.
Is there something that I might be missing?
Again, I see the header in access.log; However the same is missing from the
data send
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 11:42 AM Kedar K
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,
>> I tried to get the
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
> k-v pairs intact)
>
> Is
