On Thu, May 26, 2016 at 4:40 PM, Pinakee BIswas <[email protected]> wrote:
> Regarding the faulty request, Following are two requests for the same URL > - /heels/ - one when the user was logged in and another when the user had > logged out. The second one (when the user was logged out) is the faulty one > as the user is still seeing the data when he was logged in. > > - BereqMethod GET > - BereqURL /heels/ > - BereqProtocol HTTP/1.0 > - BereqHeader X-CLIENT-COUNTRY: IN > - BereqHeader Host: varnish_staging > - BereqHeader Accept: > text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 > - BereqHeader Upgrade-Insecure-Requests: 1 > - BereqHeader User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X > 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 > Safari/537.36 > - BereqHeader Referer: http://test.jivaana.in/home > - BereqHeader Accept-Language: en-US,en;q=0.8 > - BereqHeader X-Forwarded-For: 127.0.0.1 > - BereqHeader Accept-Encoding: gzip > - BereqProtocol HTTP/1.1 > - BereqHeader X-Varnish: 32788 > Are you sure your backend isn't caching stuff or something like that? Looking at bereq 32788, varnish is fetch a fresh object, and I see no header that would identify the user. Have you tried without varnish? -- Guillaume Quintard
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
