Skip to content

Commit

Permalink
[Docker] Update debug example to cover xkey usage
Browse files Browse the repository at this point in the history
  • Loading branch information
andrerom committed Oct 26, 2017
1 parent 0e53a01 commit 1e57f6c
Showing 1 changed file with 13 additions and 5 deletions.
18 changes: 13 additions & 5 deletions doc/docker/varnish.yml
Expand Up @@ -30,11 +30,19 @@ services:

## DEBUG??
# In need of debugging all request going to Varnish, use varnishlog, example:
# docker-compose exec varnish varnishlog -c -i ReqURL,ReqMethod -I ReqHeader:X-Location-Id
# Or more relevant only BAN's with all info:
# docker-compose exec varnish varnishlog -g request -q "ReqMethod eq 'BAN'"
# docker-compose exec varnish varnishlog -c -i ReqURL,ReqMethod -I ReqHeader:xkey
# Or more relevant only PURGE's with all info:
# docker-compose exec varnish varnishlog -g request -q "ReqMethod eq 'PURGE'"
#
# But before doing that check that http and not local purge client is set:
# docker-compose exec app app/console --env=dev debug:container ezpublish.http_cache.purge_client
# But before doing that check that http and not local purge client is set:
# docker-compose exec app app/console --env=dev debug:container ezplatform.http_cache.purge_client
#
# Or if you are using BAN requests and not using EzSystemsPlatformHttpCacheBundle:
# docker-compose exec varnish varnishlog -c -i ReqURL,ReqMethod -I ReqHeader:X-Location-Id
# Or more relevant only BAN's with all info:
# docker-compose exec varnish varnishlog -g request -q "ReqMethod eq 'BAN'"
#
# But before doing that check that http and not local purge client is set:
# docker-compose exec app app/console --env=dev debug:container ezpublish.http_cache.purge_client
#
# And if in prod make sure you have rebuilt app container on code changes ;)

0 comments on commit 1e57f6c

Please sign in to comment.