This seems to be the best solution at present for managing headers. Instead of re-writing functionality into separate modules to do largely the same thing. The thought would be to provide a setting or optional sub-moudle that would allow site maintainers to set headers via nodeapi or other criteria in cases where the sites don't need to utilize Context on the site. Other modules like http://drupal.org/project/httpHeaders exist but aren't updated to Drupal 6. It would be good to have this in one place with some sub modules...

What do you think?

Comments

febbraro’s picture

febbraro commented

Hey Josh. I think we can probably work out something, but I would be interested in seeing more of a skeleton of what you thinking.

Could be as simple as adding a Rule action that would add headers based on some event? Or were you thinking about something far more sinister?

webkenny’s picture

webkenny commented

I think that headers based on Rule actions -and- path pattern matches might be an interesting combination. A broad management of headers would be a useful addition, IMO. Perhaps it's a combination of condition and rule. i.e. If we're on this page pattern, activate the following action. Willing to assist with this as well. It's a needed item for many who don't use Context and, like Josh points out, is the cleanest and best maintained solution.

pcho’s picture

pcho commented
Status: Active » Postponed (maintainer needs more info)
pcho’s picture

pcho commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)
jbrauer’s picture

jbrauer commented
Status: Closed (cannot reproduce) » Active

Definitely something as simple as rules could manage it. As webkenny says the ideal would be combining rule matches and path matches as far as I can see. Something as "simple" as a two column interface with path patterns on the left and headers on the right ... or maybe something like the pathauto settings