Per vhost cache

[const-t]

Cache key consist of uri + host header, however may be the case when http_chains is configured to route request to other vhost regardless host header. Therefore, after routing Tempesta will try to find/build cache record using the key that belongs to another vhost(specified in host header).

Example: curl -H"Connection: close" http://app1

vhost app1 {
...
}

vhost app2 {
...
}

http_chains {
hdr "Connection" == "keep-alive" > app1;
-> app2;
}

In this case, although we requesting app1 request will be forwarded to app2, but cache record will be stored using key / app1, however expected key is / app2.

To fix this issue we must take uri + vhost name to build the cache key instead of uri + host header.

Testing

Functional test must be implemented.