Re: [users@httpd] Caching https pages in Apache ?

Issac Goldstand <margol@xxxxxxxxxxxxx> · Mon, 25 Sep 2006 10:10:39 +0300

Actually, my understanding is that mod_file_cache (unlike disk and mem) 

caches the filehandle, not the content, and is specifically meant to 

give an extra boost for serving static files that you know will be very 

popular by not having to open() them each time they're served.  So it 

may be what you want.  Since SSL happens at the protocol/connection 

filter level, and mod_cache at the request/protocol level, there's no 

reason it shouldn't.

See http://httpd.apache.org/docs/2.2/mod/mod_file_cache.html

 Issac

Joshua Slive wrote:

On 9/22/06, ABAPGUY <abapguy@xxxxxxxxx> wrote:

is there any point using mod_cache , mod_file_cache on an Apache 2 

server

that only serves https pages ?
In other words can https pages be cache in Apache ?

It is my understanding that the encryption itself cannot be cached
because there is a unique encryption key for each client.  (Someone
please correct me if I'm wrong.)  But the cache can still help if you
have heavy-weight content generation, since it will cache a complete,
unencrypted copy of the page.  If you are just serving static files,
it probably won't do much good.

Joshua.

---------------------------------------------------------------------

The official User-To-User support forum of the Apache HTTP Server 

Project.

See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx