The module page explains what it does, but doesn't really explain when and why we would want to use it (to change HTTP-headers).

I know the reasons to change the headers might vary wildly, and I also know of several potential use cases. I for example would primarily use this module for very specific varnish cache purging. I mean we could for example:

1. tag some nodes with a few keywords
2. create a context that activates on a specific library (or a part of it)
3. create a header that includes those tags (using this modules' hooks in my own module)

For example: "Content-tags: performance--speed--hacks--geeky"

After that I would use the ability of varnish to clear caches with regexp that matches a part of the custom HTTP-header.
In other words, I could clear the cache of all pages that have nodes tagged with the word "performance".

This is just a theory for me currently, but do you happen to use this same approach?

Comments

pcho’s picture

pcho commented

bibo,

I believe the module was originally intended to supplement the akamai module, but considering you can virtually set any http headers, you could be creative with how you interact with your own custom-made headers.

bibo’s picture

bibo commented
Status: Active » Closed (works as designed)

you could be creative with how you interact with your own custom-made headers.

Thanks, that's exactly what I plan to do with my module in progress :)