WA and HEAD request

I noticed that the only methods I can specify in a policy configuration are GET and POST. If a browser sends a HEAD request for an image (content that is cached), would I not expect that to be served by WA as well. Can anyone think of a reason why I would not want to have the WA respond to the HEAD request?

 

 

Thanks,

 

 

Tom Schaefer