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 to store-id helper. On Wed, Jul 11, 2018 at 3:29 PM Kedar K <mailbox.ke...@gmail.com> 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 <mailbox.ke...@gmail.com> 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 <mailbox.ke...@gmail.com> 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 <mailbox.ke...@gmail.com> >>> 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 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 either as part of URL (append at >>>> the end) or request header. >>>> >>>> Is it possible to use combination of store_id_program helper and >>>> rewrite_url_program; such that the extra params from the url are used by >>>> store-id helper to create a store-id and then the url_rewrite program can >>>> strip them off before sending the request to origin server? >>>> >>>> >>>> -- >>>> >>>> *- Kedar* >>>> >>> >>> >>> -- >>> >>> >>> >> >> -- >> >> >>
_______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users