mod_headers seems to be a requirement [#762756]

I followed the instructions to install the module in a drupal site installed on a local apache server. After all the process in status report I found a Boost message:

"The Apache module "mod_headers" is not available. You must enable mod_headers for Apache."

Maybe is a common apache mod on hosting web servers, I don't know, but by default in my local server it was not enabled. Shouldn't it be listed as a requirement on readme.txt.

At least for me without that apache mod (mod_headers) my drupal local installations works fine and with clean URLs working fine too without that mod, so it doesn't seem to be a drupal or clean URLs requirement at all but a boost requirement.

Comment	File	Size	Author
#5	boost-762756.patch	1.18 KB	mikeytown2
#5

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

mikeytown2 CreditAttribution: mikeytown2 commented 5 April 2010 at 23:40

try the latest dev, It's no longer a strict requirement; reminds me, need to fix the status report so its yellow instead of red when this happens. Or is it yellow right now?

Comment #2

manfer CreditAttribution: manfer commented 6 April 2010 at 09:25

I disabled mod_headers again to look at status report.

It is a yellow warning saying: "The Apache module "mod_headers" is not available. You must enable mod_headers for Apache."

I really hadn't paid attention to the colour of the warning. As I had read "you must" I suppposed the module was not working without that apache mod enabled.

You mean boost works without that mod? What is the difference then on having that mod or not?

Comment #3

mikeytown2 CreditAttribution: mikeytown2 commented 6 April 2010 at 16:34

The headers are not exactly what they are supposed to be and 1 feature doesn't work. There is also a slight chance for the browser to cache a page & thus when you login you get a page from boost instead of a live page.

Comment #4

bbeyer CreditAttribution: bbeyer commented 11 October 2010 at 19:04

I was wondering about this too. So is mod_headers required or not? As stated above, "you must" should be removed from the status report page.

Comment #5

mikeytown2 CreditAttribution: mikeytown2 commented 12 October 2010 at 02:44

Status:

Active

» Fixed

File	Size
boost-762756.patch	1.18 KB

fixed the wording of this.

The Apache module "mod_headers" is not available. Enable mod_headers for Apache if at all possible.

Let me know if you come up with a better way to say it.

Comment #6

mikeytown2 CreditAttribution: mikeytown2 commented 12 October 2010 at 02:44

Version:

6.x-1.18

» 6.x-1.x-dev

Comment #7

bbeyer CreditAttribution: bbeyer commented 12 October 2010 at 15:53

Sounds good to me. But can you please explain what is gained when mod_headers is available versus when it isn't available.

Comment #8

mikeytown2 CreditAttribution: mikeytown2 commented 12 October 2010 at 17:59

  <IfModule mod_headers.c>
    Header set Expires "Sun, 19 Nov 1978 05:00:00 GMT"
    Header set Cache-Control "no-store, no-cache, must-revalidate, post-check=0, pre-check=0"
    Header set X-Header "Boost Citrus 1.8"
  </IfModule>

Gives you the cache-control and expires headers. Also can give you the boost x-header to let you know that this file was served from the cache. In short mod_headers can make the output of boost closely mimic the output of a page from the Drupal cache; trying to be as seamless as possible.