[cache tagging] OPTIONS call invalidates tags

[wickedOne]

currently, when doing an OPTIONS call to a specific route which is configured for tagging, this code invalidates the related / generated tags.

i'm aware that you can easily circumvent this behaviour by adding a match like this to the top of your config:

-
  match:
      path: ^/
      methods:
          - OPTIONS

but am wondering, looking at the specifications for the OPTIONS call, whether this is desired behaviour

[dbu]

hm, interesting. i guess options could usually even be cached. but probably the HTTP specification does not guarantee this, so its considered not safe.

if memory serves correctly, #69 would provide a way to solve this (see also #241) by offering more flexibility.

[ddeboer]

Fixed in #354.