Is searx.priv.pw caching requests?

[ononoki1]

Hi @vvaadim

I noticed your instance has a very low response time on searx.space (0.032s).

Then I made requests via curl (curl -I https://searx.priv.pw/search?q=test) and found the server-timing header is exactly the same for every request (server-timing: total;dur=866.878, render;dur=93.941, total_0_wikipedia;dur=225.956, total_1_bing;dur=406.301, total_2_google;dur=759.098, load_0_wikipedia;dur=222.546, load_1_bing;dur=385.66, load_2_google;dur=700.7), which is hardly possible in normal case.

Caching requests is not privacy-friendly, and it also violates the promise you made when adding instance (see here: #67 (comment)). Of course I might be wrong, but would you like to give an explanation?

[vvaadim]

Hey, you are right. I was experimenting with Nginx caching to speed up my instance a bit, no logs were retained eitherway and mostly static objects were being cached. Thanks for letting me know, I did not know that it was an issue. I have removed it. Sorry,