You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modules-dev@httpd.apache.org by Erica Zhang <er...@cs.ubc.ca> on 2007/03/06 07:53:20 UTC
Questions on modules to provide cache functions for Apache
Hi,
I want to develop a filter module to cache responses for XMLHttp
requests for Apache. Before that, I have tried to configure using
mod_cache. I found that it could not be used to cache responses for
XMLHttp requests. However, I am not sure about this, because I am new to
web applications. So before beginning to develop a new module to do this
function, I want to make sure that. Is there some expert tell me about
your idea on this topic or experiences ?
I tried to give more details below:
For mod_cache, I use httpd.conf to configure it:
MaxKeepAliveRequests 10000
<IfModule mpm_winnt.c>
ThreadsPerChild 1900
MaxRequestsPerChild 10000
</IfModule>
LoadModule cache_module modules/mod_cache.so
<IfModule mod_cache.c>
CacheForceCompletion 100
CacheDefaultEXPire 3600
CacheMaxExpire 86400
CacheLastModifiedFactor 0.1
LoadModule disk_cache_module modules/mod_disk_cache.so
<IfModule mod_disk_cache.c>
CacheEnable disk /
CacheRoot c:/cacheroot
CacheSize 327680
CacheDirLength 4
CacheDirLevels 5
CacheGcInterval 4
</IfModule>
#LoadModule mem_cache_module modules/mod_mem_cache.so
<IfModule mod_mem_cache.c>
CacheEnable mem /
MCacheSize 8192
MCacheMaxObjectCount 10000
MCacheMinObjectSize 1
MCacheMaxObjectSize 51200
</IfModule>
</IfModule>
On client, I use ajax technology and XMLHttpRequest and on server, I
use php script.
...
header("Cache-Control: public"); // HTTP/1.1
header("Expires: " .gmdate ("D, d M Y H:i:s", time() + 60 * 10). " GMT");
header( "Last-Modified: " .gmdate( 'D, d M Y H:i:s' ). " GMT" );
echo $response;
....
I think apache cache should catch my response produced by PHP. Until
now, I do not think there is something wrong in my code or
configuration. So I conclude that mod_cache could not catch the
responses for XMLHttp requests.
Regards,
Erica
Re: Questions on modules to provide cache functions for Apache
Posted by Joe Lewis <jo...@joe-lewis.com>.
Erica Zhang wrote:
> No, still not work. Infact, mod_cache could work, because it could
> cache the javascript. But it could not work for dynamic HTTP responses
> responding to XMLHttpRequests in Ajax technology. So I suspect
> mod_cache could not support this function. And I need provide such
> function by myself. I prefer to do it in Apache, a comparatively
> general way instead of application itself.
The reason it does not cache the dynamic responses is because those
headers (Expires, Cache-Control and Last-Modifed) do NOT exist with that
content. In that situation again, you have two options :
a) modify the generator (the java class generating the XML data) to
supply a last-modifed header.
b) blind cache it - again causing discrepancies in data at the browser
and data supplied by the server.
It is always suggested that, if the data is to be cached, the generator
needs to submit the appropriate caching headers. If the headers are not
submitted by the generator and something does cache it without checking
for updates at the server, don't expect "up-to-date" hits on this
dynamic data from a browsers' perspective - it simply cannot happen.
Joe
--
Joseph Lewis <http://sharktooth.org/>
"Divide the fire, and you will sooner put it out." - Publius Syrus
Re: Questions on modules to provide cache functions for Apache
Posted by Joachim Zobel <jz...@heute-morgen.de>.
Am Dienstag, den 06.03.2007, 11:42 -0800 schrieb Erica Zhang:
> No, still not work. Infact, mod_cache could work, because it could cache
> the javascript. But it could not work for dynamic HTTP responses
> responding to XMLHttpRequests in Ajax technology. So I suspect mod_cache
> could not support this function. And I need provide such function by
> myself. I prefer to do it in Apache, a comparatively general way instead
> of application itself.
Why do you think it can not work? Apache does not know the requests are
done with XMLHttpRequest. By the way, how do you know it does not work?
You may want to use Firefox with the LiveHttpHeaders Plugin to look at
the headers, that are actually exchanged (or are you already doing
that).
Sincerely,
Joachim
Re: Questions on modules to provide cache functions for Apache
Posted by Joachim Zobel <jz...@heute-morgen.de>.
Am Dienstag, den 06.03.2007, 14:41 -0800 schrieb Erica Zhang:
> I use live http headers to catch the headers. I listed them below. Well
> I found that php file has not been given the http headers. So is this
> the problem for not caching the response produced by it ?
Yes, see http://httpd.apache.org/docs/2.2/caching.html
"If the URL included a query string (e.g. from a HTML form GET method)
it will not be cached unless the response includes an "Expires:" header,
as per RFC2616 section 13.9."
Sincerely,
Joachim
Re: Questions on modules to provide cache functions for Apache
Posted by Erica Zhang <er...@cs.ubc.ca>.
I tried to use apache 2.2.4. Then mod_cache could catch the reponses. So
I do not need to develop a filter for this function. :-)
Thanks a lot for your help.
Erica Zhang wrote:
> OK. For javascript file, I could find the files of Header and Data
> under the directory of mod_disk_cache. For php file, I could not find
> it. To enable you to get more details, you could access the simple
> application by yourself through http://128.189.138.12 (I am not sure
> if you could access it.) Also, I attach my http.conf, clienthint.js
> and gethint.php to this email.
>
> I really do not know why it could not work. BTW: I deploy the Apache
> server on the Windows XP.
>
> Regards,
>
> Erica
>
> David Wortham wrote:
>
>> Erica,
>> I'm out of ideas. I get the feeling that there's something you aren't
>> telling us, but I feel that we have checked all the obvious points.
>>
>> I mis-typed the module name. I meant mod_disk_cache when I said
>> mod_file_cache.
>>
>> Dave
>>
>>
>>
>>
>>
>> On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>>
>>>
>>> David,
>>>
>>> 1) I tried /gethint.php without any GET/POST parameters. I got nothing
>>> and it could not be cached even with force-caching directive. I do the
>>> same thing for clienthint.js. It could work and display the source code
>>> and could be cached.
>>>
>>> 2), The first part is the responses for clienthint.js:
>>>
>>> HTTP/1.x 200 OK
>>> Date: Wed, 07 Mar 2007 00:05:08 GMT
>>> Server: Apache/2.0.59 (Win32)
>>> Last-Modified: Tue, 06 Mar 2007 01:57:50 GMT
>>> *Etag: "88a26cc0-3ed-66b16380"*
>>> *Accept-Ranges: bytes
>>> Content-Length: 1005*
>>> Keep-Alive: timeout=15, max=9999
>>> Connection: Keep-Alive
>>> *Content-Type: application/x-javascript*
>>>
>>> The second part is the response for gethint.php:
>>>
>>> HTTP/1.x 200 OK
>>> Date: Wed, 07 Mar 2007 00:06:12 GMT
>>> Server: Apache/2.0.59 (Win32)
>>> X-Powered-By: PHP/4.4.4
>>> Cache-Control: public
>>> *Expires: Wed, 07 Mar 2007 00:16:12 GMT*
>>> Last-Modified: Wed, 07 Mar 2007 00:06:12 GMT
>>> Keep-Alive: timeout=15, max=10000
>>> Connection: Keep-Alive
>>> *Transfer-Encoding: chunked
>>> Content-Type: text/html*
>>>
>>> I make the different header parts in bold.
>>>
>>> 3) Do you think I need to use mod_file_cache ? I do not use it.
>>>
>>> Regards,
>>>
>>> Erica
>>>
>>>
>>> David Wortham wrote:
>>>
>>> > Erica,
>>> > My only comments: either
>>> > (1) the request parameters are killing mod_cache's desire to cache
>>> the
>>> > file
>>> > or
>>> > (2) something is different in the headers between your JavaScript and
>>> PHP
>>> > responses.
>>> >
>>> > I would:
>>> > (1) Try requesting /gethint.php without any GET/POST parameters (your
>>> app
>>> > should respond with correctly formatted XML [probably returning an
>>> error
>>> > code]). Is this file cached (with/without the force-caching
>>> directive)?
>>> > (2) Compare the javascript and xml response headers and compare any
>>> > differences. I would think forcing mod_cache to ignore all headers
>>> would
>>> > make this trivial... but this may reveal something which may be
>>> missing.
>>> > (3) Clear your cache directory and see if your XML response creates a
>>> > file,
>>> > then check if your javascript file creates a cache file (assuming you
>>> are
>>> > still using mod_file_cache)
>>> >
>>> > Regards,
>>> > Dave
>>> >
>>> >
>>> > On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>>> >
>>> >>
>>> >> Yes. I changed the PHP script. Now I change them back and also set
>>> >> CacheIgnoreCacheControl On. And still could not work. For other
>>> >> questions, please see the my answers below. Thanks.
>>> >>
>>> >> David Wortham wrote:
>>> >>
>>> >> > Erica,
>>> >> > My observations of your headers:
>>> >> > (1) The "Last-Modified" line contains the current timestamp (as
>>> >> expected)
>>> >>
>>> >> After I set CacheIgnoreCacheControl On, it does not matter. Right ?
>>> >> Although I move the headers to the top code, it still could not
>>> work.
>>> >>
>>> >> > (2) Your original question showed that you inserted an "Expires:"
>>> >> header,
>>> >> > but it doesn't show in your response. Did you change your PHP
>>> script
>>> >> > code
>>> >> > since you asked the original question this morning?
>>> >>
>>> >> Yes. It is my fault.
>>> >>
>>> >> > (3) Are you returning XML or HTML? My experience with
>>> >> XMLHttpResponse(s)
>>> >> > required changing the content-type to "text/xml" (not really the
>>> issue
>>> >> at
>>> >> > hand)
>>> >> >
>>> >> Does it matter ?
>>> >>
>>> >> > When you said that you got mod_cache to cache a JavaScript
>>> file, was
>>> >> > it in
>>> >> > the same directory (and covered by the same mod_cache directives)?
>>> >>
>>> >> Yes, both javascript file and the php file are under htdocs
>>> directory.
>>> >>
>>> >> >
>>> >> > Did you try using the
>>> >> > CacheIgnoreCacheControl On
>>> >> > directive? Did it force the file to cache?
>>> >>
>>> >> I tried. But it could not work.
>>> >>
>>> >> >
>>> >> > Regards,
>>> >> > Dave
>>> >> >
>>> >> >
>>> >> > On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>>> >> >
>>> >> >>
>>> >> >> I use live http headers to catch the headers. I listed them
>>> below.
>>> >> Well
>>> >> >> I found that php file has not been given the http headers. So is
>>> this
>>> >> >> the problem for not caching the response produced by it ? Then
>>> how
>>> >> can
>>> >> I
>>> >> >> handle this problem ? Also, is there some mod_cache log that I
>>> could
>>> >> >> refer ? Thanks.
>>> >> >>
>>> >> >> http://128.189.246.64/gethint.php?q=Eric&sid=0.11837499670287688
>>> >> >>
>>> >> >> GET /gethint.php?q=Eric&sid=0.11837499670287688 HTTP/1.1
>>> >> >> Host: 128.189.246.64
>>> >> >> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>>> >> rv:1.8.1.2)
>>> >> >> Gecko/20070219 Firefox/2.0.0.2
>>> >> >> Accept:
>>> >> >> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9
>>> >> >> ,text/plain;q=0.8,image/png,*/*;q=0.5
>>> >> >> Accept-Language: en-us,en;q=0.5
>>> >> >> Accept-Encoding: gzip,deflate
>>> >> >> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>>> >> >> Keep-Alive: 300
>>> >> >> Connection: keep-alive
>>> >> >> Referer: http://128.189.246.64/
>>> >> >>
>>> >> >> HTTP/1.x 200 OK
>>> >> >> Date: Tue, 06 Mar 2007 22:35:34 GMT
>>> >> >> Server: Apache/2.0.59 (Win32)
>>> >> >> X-Powered-By: PHP/4.4.4
>>> >> >> Cache-Control: public
>>> >> >> Last-Modified: Tue, 06 Mar 2007 22:35:34 GMT
>>> >> >> Keep-Alive: timeout=15, max=10000
>>> >> >> Connection: Keep-Alive
>>> >> >> Transfer-Encoding: chunked
>>> >> >> Content-Type: text/html
>>> >> >>
>>> >> >>
>>> >> >> Erica Zhang wrote:
>>> >> >>
>>> >> >> > Well, even I use the blinding-cache. It still could not work.
>>> >> Thanks,
>>> >> >> >
>>> >> >> > Erica
>>> >> >> >
>>> >> >> > David Wortham wrote:
>>> >> >> >
>>> >> >> >> Erica,
>>> >> >> >> I'm not sure why mod_cache should not be able to work
>>> (assuming
>>> >> >> your
>>> >> >> >> module and pages are configured correctly).
>>> >> >> >>
>>> >> >> >> IIRC, JavaScript is used on the presentation request
>>> (with the
>>> >> >> >> webpage),
>>> >> >> >> whereas the XMLHttpRequest response is a PHP-generated XML
>>> >> document.
>>> >> >> >> Perhaps your extension ('.php" maybe?) or the
>>> mime/content-type
>>> >> >> >> ("text/xml")
>>> >> >> >> is what is causing mod_cache to skip the file?
>>> >> >> >>
>>> >> >> >> Also, from what I can gather, using mod_cache with mod_proxy
>>> >> (as a
>>> >> >> >> caching proxy) can alter the effects of mod_cache slightly.
>>> >> You may
>>> >> >> >> want to
>>> >> >> >> read up on that.
>>> >> >> >>
>>> >> >> >> Try using the following directive with mod_cache:
>>> >> >> >> CacheIgnoreNoLastMod On
>>> >> >> >>
>>> >> >> >> see:
>>> >> >> >>
>>> >> >>
>>> >>
>>> http://webauth.stanford.edu/manual/mod/mod_cache.html#CacheIgnoreNoLastMod
>>>
>>> >>
>>> >> >>
>>> >> >> >>
>>> >> >> >>
>>> >> >> >> This apparently forces blind-caching which Joe suggests is
>>> bad (I
>>> >> >> >> don't know
>>> >> >> >> anything about it). Short of that, you just need to read the
>>> >> >> mod_cache
>>> >> >> >> manual and make sure your XML response contains the necessary
>>> >> headers
>>> >> >> >> to get
>>> >> >> >> mod_cache to work correctly.
>>> >> >> >>
>>> >> >> >> Regards,
>>> >> >> >> Dave
>>> >> >> >>
>>> >> >> >>
>>> >> >> >>
>>> >> >> >> On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>>> >> >> >>
>>> >> >> >>>
>>> >> >> >>> No, still not work. Infact, mod_cache could work, because it
>>> >> could
>>> >> >> >>> cache
>>> >> >> >>> the javascript. But it could not work for dynamic HTTP
>>> responses
>>> >> >> >>> responding to XMLHttpRequests in Ajax technology. So I
>>> suspect
>>> >> >> >>> mod_cache
>>> >> >> >>> could not support this function. And I need provide such
>>> function
>>> >> by
>>> >> >> >>> myself. I prefer to do it in Apache, a comparatively
>>> general way
>>> >> >> >>> instead
>>> >> >> >>> of application itself.
>>> >> >> >>>
>>> >> >> >>>
>>> >> >> >>> Erica
>>> >> >> >>>
>>> >> >> >>> Joachim Zobel wrote:
>>> >> >> >>>
>>> >> >> >>> >Am Montag, den 05.03.2007, 22:53 -0800 schrieb Erica Zhang:
>>> >> >> >>> >
>>> >> >> >>> >
>>> >> >> >>> >>header("Cache-Control: public"); // HTTP/1.1
>>> >> >> >>> >>header("Expires: " .gmdate ("D, d M Y H:i:s", time() + 60 *
>>> >> 10).
>>> >> "
>>> >> >> >>> GMT");
>>> >> >> >>> >>header( "Last-Modified: " .gmdate( 'D, d M Y H:i:s' ). "
>>> >> GMT" );
>>> >> >> >>> >>echo $response;
>>> >> >> >>> >>
>>> >> >> >>> >>
>>> >> >> >>> >
>>> >> >> >>> >I am not shure about mod_caches behaviour, but omitting
>>> >> >> >>> last-modified is
>>> >> >> >>> >worth a try.
>>> >> >> >>> >
>>> >> >> >>> >Sincerely,
>>> >> >> >>> >Joachim
>>> >> >> >>> >
>>> >> >> >>> >
>>> >> >> >>> >
>>> >> >> >>>
>>> >> >> >>>
>>> >> >> >>
>>> >> >>
>>> >> >>
>>> >> >
>>> >>
>>> >>
>>> >
>>>
>>>
>>
>
>------------------------------------------------------------------------
>
>
>var xmlHttp
>
>function showHint(str)
>{
>if (str.length==0)
> {
> document.getElementById("txtHint").innerHTML="";
> alert(xmlHttp.getAllResponseHeaders());
> return;
> }
>xmlHttp=GetXmlHttpObject()
>if (xmlHttp==null)
> {
> alert ("Your browser does not support AJAX!");
> return;
> }
>var url="gethint.php";
>url=url+"?q="+str;
>url=url+"&sid="+Math.random();
>xmlHttp.onreadystatechange=stateChanged;
>xmlHttp.open("GET",url,true);
>xmlHttp.send(null);
>}
>
>function stateChanged()
>{
>if (xmlHttp.readyState==4)
>{
>document.getElementById("txtHint").innerHTML = xmlHttp.responseText;
>alert(xmlHttp.getAllResponseHeaders());
>}
>}
>
>function GetXmlHttpObject()
>{
>var xmlHttp=null;
>try
> {
> // Firefox, Opera 8.0+, Safari
> xmlHttp=new XMLHttpRequest();
> }
>catch (e)
> {
> // Internet Explorer
> try
> {
> xmlHttp=new ActiveXObject("Msxml2.XMLHTTP");
> }
> catch (e)
> {
> xmlHttp=new ActiveXObject("Microsoft.XMLHTTP");
> }
> }
>return xmlHttp;
>}
>
>------------------------------------------------------------------------
>
>#
># Based upon the NCSA server configuration files originally by Rob McCool.
>#
># This is the main Apache server configuration file. It contains the
># configuration directives that give the server its instructions.
># See <URL:http://httpd.apache.org/docs/2.0/> for detailed information about
># the directives.
>#
># Do NOT simply read the instructions in here without understanding
># what they do. They're here only as hints or reminders. If you are unsure
># consult the online docs. You have been warned.
>#
># The configuration directives are grouped into three basic sections:
># 1. Directives that control the operation of the Apache server process as a
># whole (the 'global environment').
># 2. Directives that define the parameters of the 'main' or 'default' server,
># which responds to requests that aren't handled by a virtual host.
># These directives also provide default values for the settings
># of all virtual hosts.
># 3. Settings for virtual hosts, which allow Web requests to be sent to
># different IP addresses or hostnames and have them handled by the
># same Apache server process.
>#
># Configuration and logfile names: If the filenames you specify for many
># of the server's control files begin with "/" (or "drive:/" for Win32), the
># server will use that explicit path. If the filenames do *not* begin
># with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
># with ServerRoot set to "C:/Program Files/Apache Group/Apache2" will be interpreted by the
># server as "C:/Program Files/Apache Group/Apache2/logs/foo.log".
>#
># NOTE: Where filenames are specified, you must use forward slashes
># instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
># If a drive letter is omitted, the drive on which Apache.exe is located
># will be used by default. It is recommended that you always supply
># an explicit drive letter in absolute paths, however, to avoid
># confusion.
>#
>
>### Section 1: Global Environment
>#
># The directives in this section affect the overall operation of Apache,
># such as the number of concurrent requests it can handle or where it
># can find its configuration files.
>#
>
>#
># ServerRoot: The top of the directory tree under which the server's
># configuration, error, and log files are kept.
>#
># NOTE! If you intend to place this on an NFS (or otherwise network)
># mounted filesystem then please read the LockFile documentation (available
># at <URL:http://httpd.apache.org/docs/2.0/mod/mpm_common.html#lockfile>);
># you will save yourself a lot of trouble.
>#
># Do NOT add a slash at the end of the directory path.
>#
>ServerRoot "C:/Program Files/Apache Group/Apache2"
>
>#
># ScoreBoardFile: File used to store internal server process information.
># If unspecified (the default), the scoreboard will be stored in an
># anonymous shared memory segment, and will be unavailable to third-party
># applications.
># If specified, ensure that no two invocations of Apache share the same
># scoreboard file. The scoreboard file MUST BE STORED ON A LOCAL DISK.
>#
>#ScoreBoardFile logs/apache_runtime_status
>
>#
># PidFile: The file in which the server should record its process
># identification number when it starts.
>#
>PidFile logs/httpd.pid
>
>#
># Timeout: The number of seconds before receives and sends time out.
>#
>Timeout 300
>
>#
># KeepAlive: Whether or not to allow persistent connections (more than
># one request per connection). Set to "Off" to deactivate.
>#
>KeepAlive On
>
>#
># MaxKeepAliveRequests: The maximum number of requests to allow
># during a persistent connection. Set to 0 to allow an unlimited amount.
># We recommend you leave this number high, for maximum performance.
>#
>MaxKeepAliveRequests 100
>
>#
># KeepAliveTimeout: Number of seconds to wait for the next request from the
># same client on the same connection.
>#
>KeepAliveTimeout 15
>
>##
>## Server-Pool Size Regulation (MPM specific)
>##
>
># WinNT MPM
># ThreadsPerChild: constant number of worker threads in the server process
># MaxRequestsPerChild: maximum number of requests a server process serves
><IfModule mpm_winnt.c>
>ThreadsPerChild 250
>MaxRequestsPerChild 0
></IfModule>
>
>#
># Listen: Allows you to bind Apache to specific IP addresses and/or
># ports, instead of the default. See also the <VirtualHost>
># directive.
>#
># Change this to Listen on specific IP addresses as shown below to
># prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
>#
>#Listen 12.34.56.78:80
>Listen 80
>
>
>#
># Dynamic Shared Object (DSO) Support
>#
># To be able to use the functionality of a module which was built as a DSO you
># have to place corresponding `LoadModule' lines at this location so the
># directives contained in it are actually available _before_ they are used.
># Statically compiled modules (those listed by `httpd -l') do not need
># to be loaded here.
>#
># Example:
># LoadModule foo_module modules/mod_foo.so
>#
>LoadModule access_module modules/mod_access.so
>LoadModule actions_module modules/mod_actions.so
>LoadModule alias_module modules/mod_alias.so
>LoadModule asis_module modules/mod_asis.so
>LoadModule auth_module modules/mod_auth.so
>#LoadModule auth_anon_module modules/mod_auth_anon.so
>#LoadModule auth_dbm_module modules/mod_auth_dbm.so
>#LoadModule auth_digest_module modules/mod_auth_digest.so
>LoadModule autoindex_module modules/mod_autoindex.so
>#LoadModule cern_meta_module modules/mod_cern_meta.so
>LoadModule cgi_module modules/mod_cgi.so
>#LoadModule dav_module modules/mod_dav.so
>#LoadModule dav_fs_module modules/mod_dav_fs.so
>LoadModule dir_module modules/mod_dir.so
>LoadModule env_module modules/mod_env.so
>LoadModule expires_module modules/mod_expires.so
>#LoadModule file_cache_module modules/mod_file_cache.so
>LoadModule headers_module modules/mod_headers.so
>LoadModule imap_module modules/mod_imap.so
>LoadModule include_module modules/mod_include.so
>#LoadModule info_module modules/mod_info.so
>LoadModule isapi_module modules/mod_isapi.so
>LoadModule log_config_module modules/mod_log_config.so
>LoadModule mime_module modules/mod_mime.so
>#LoadModule mime_magic_module modules/mod_mime_magic.so
>#LoadModule proxy_module modules/mod_proxy.so
>#LoadModule proxy_connect_module modules/mod_proxy_connect.so
>#LoadModule proxy_http_module modules/mod_proxy_http.so
>#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
>LoadModule negotiation_module modules/mod_negotiation.so
>#LoadModule rewrite_module modules/mod_rewrite.so
>LoadModule setenvif_module modules/mod_setenvif.so
>#LoadModule speling_module modules/mod_speling.so
>#LoadModule status_module modules/mod_status.so
>#LoadModule unique_id_module modules/mod_unique_id.so
>LoadModule userdir_module modules/mod_userdir.so
>#LoadModule usertrack_module modules/mod_usertrack.so
>#LoadModule vhost_alias_module modules/mod_vhost_alias.so
>#LoadModule ssl_module modules/mod_ssl.so
>
>LoadModule deflate_module modules/mod_deflate.so
>
>#
># ExtendedStatus controls whether Apache will generate "full" status
># information (ExtendedStatus On) or just basic information (ExtendedStatus
># Off) when the "server-status" handler is called. The default is Off.
>#
>#ExtendedStatus On
>
>### Section 2: 'Main' server configuration
>#
># The directives in this section set up the values used by the 'main'
># server, which responds to any requests that aren't handled by a
># <VirtualHost> definition. These values also provide defaults for
># any <VirtualHost> containers you may define later in the file.
>#
># All of these directives may appear inside <VirtualHost> containers,
># in which case these default settings will be overridden for the
># virtual host being defined.
>#
>
>#
># ServerAdmin: Your address, where problems with the server should be
># e-mailed. This address appears on some server-generated pages, such
># as error documents. e.g. admin@your-domain.com
>#
>ServerAdmin ericazhj@cs.ubc.ca
>
>#
># ServerName gives the name and port that the server uses to identify itself.
># This can often be determined automatically, but we recommend you specify
># it explicitly to prevent problems during startup.
>#
># If this is not set to valid DNS name for your host, server-generated
># redirections will not work. See also the UseCanonicalName directive.
>#
># If your host doesn't have a registered DNS name, enter its IP address here.
># You will have to access it by its address anyway, and this will make
># redirections work in a sensible way.
>#
>ServerName 128.189.138.12:80
>
>#
># UseCanonicalName: Determines how Apache constructs self-referencing
># URLs and the SERVER_NAME and SERVER_PORT variables.
># When set "Off", Apache will use the Hostname and Port supplied
># by the client. When set "On", Apache will use the value of the
># ServerName directive.
>#
>UseCanonicalName Off
>
>#
># DocumentRoot: The directory out of which you will serve your
># documents. By default, all requests are taken from this directory, but
># symbolic links and aliases may be used to point to other locations.
>#
>DocumentRoot "C:/Program Files/Apache Group/Apache2/htdocs"
>
>#
># Each directory to which Apache has access can be configured with respect
># to which services and features are allowed and/or disabled in that
># directory (and its subdirectories).
>#
># First, we configure the "default" to be a very restrictive set of
># features.
>#
><Directory />
> Options All
> AllowOverride All
></Directory>
>
>#
># Note that from this point forward you must specifically allow
># particular features to be enabled - so if something's not working as
># you might expect, make sure that you have specifically enabled it
># below.
>#
>
>#
># This should be changed to whatever you set DocumentRoot to.
>#
><Directory "C:/Program Files/Apache Group/Apache2/htdocs">
>
>#
># Possible values for the Options directive are "None", "All",
># or any combination of:
># Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
>#
># Note that "MultiViews" must be named *explicitly* --- "Options All"
># doesn't give it to you.
>#
># The Options directive is both complicated and important. Please see
># http://httpd.apache.org/docs/2.0/mod/core.html#options
># for more information.
>#
> Options All
>#Indexes FollowSymLinks
>
>#
># AllowOverride controls what directives may be placed in .htaccess files.
># It can be "All", "None", or any combination of the keywords:
># Options FileInfo AuthConfig Limit
>#
> AllowOverride All
>
>#
># Controls who can get stuff from this server.
>#
> Order allow,deny
> Allow from all
>
></Directory>
>
>#
># UserDir: The name of the directory that is appended onto a user's home
># directory if a ~user request is received. Be especially careful to use
># proper, forward slashes here. On Windows NT, "Personal/My Website"
># is a more appropriate choice.
>#
>UserDir "My Documents/My Website"
>
>#
># Control access to UserDir directories. The following is an example
># for a site where these directories are restricted to read-only.
>#
># You must correct the path for the root to match your system's configured
># user directory location, e.g. "C:/WinNT/profiles/*/My Documents/My Website"
># or whichever, as appropriate.
>#
>#<Directory "C:/Documents and Settings/*/My Documents/My Website">
># AllowOverride FileInfo AuthConfig Limit
># Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
># <Limit GET POST OPTIONS PROPFIND>
># Order allow,deny
># Allow from all
># </Limit>
># <LimitExcept GET POST OPTIONS PROPFIND>
># Order deny,allow
># Deny from all
># </LimitExcept>
>#</Directory>
>
>#
># DirectoryIndex: sets the file that Apache will serve if a directory
># is requested.
>#
># The index.html.var file (a type-map) is used to deliver content-
># negotiated documents. The MultiViews Option can be used for the
># same purpose, but it is much slower.
>#
>DirectoryIndex ericazhj.html index.html index.html.var index.php
>
>#
># AccessFileName: The name of the file to look for in each directory
># for additional configuration directives. See also the AllowOverride
># directive.
>#
>AccessFileName .htaccess
>
>#
># The following lines prevent .htaccess and .htpasswd files from being
># viewed by Web clients.
>#
><FilesMatch "^\.ht">
> Order allow,deny
> Deny from all
></FilesMatch>
>
>#
># TypesConfig describes where the mime.types file (or equivalent) is
># to be found.
>#
>TypesConfig conf/mime.types
>
>#
># DefaultType is the default MIME type the server will use for a document
># if it cannot otherwise determine one, such as from filename extensions.
># If your server contains mostly text or HTML documents, "text/plain" is
># a good value. If most of your content is binary, such as applications
># or images, you may want to use "application/octet-stream" instead to
># keep browsers from trying to display binary files as though they are
># text.
>#
>DefaultType text/plain
>
>#
># The mod_mime_magic module allows the server to use various hints from the
># contents of the file itself to determine its type. The MIMEMagicFile
># directive tells the module where the hint definitions are located.
>#
><IfModule mod_mime_magic.c>
> MIMEMagicFile conf/magic
></IfModule>
>
>#
># HostnameLookups: Log the names of clients or just their IP addresses
># e.g., www.apache.org (on) or 204.62.129.132 (off).
># The default is off because it'd be overall better for the net if people
># had to knowingly turn this feature on, since enabling it means that
># each client request will result in AT LEAST one lookup request to the
># nameserver.
>#
>HostnameLookups Off
>
>#
># EnableMMAP: Control whether memory-mapping is used to deliver
># files (assuming that the underlying OS supports it).
># The default is on; turn this off if you serve from NFS-mounted
># filesystems. On some systems, turning it off (regardless of
># filesystem) can improve performance; for details, please see
># http://httpd.apache.org/docs/2.0/mod/core.html#enablemmap
>#
>#EnableMMAP off
>
>#
># EnableSendfile: Control whether the sendfile kernel support is
># used to deliver files (assuming that the OS supports it).
># The default is on; turn this off if you serve from NFS-mounted
># filesystems. Please see
># http://httpd.apache.org/docs/2.0/mod/core.html#enablesendfile
>#
>#EnableSendfile off
>
>#
># ErrorLog: The location of the error log file.
># If you do not specify an ErrorLog directive within a <VirtualHost>
># container, error messages relating to that virtual host will be
># logged here. If you *do* define an error logfile for a <VirtualHost>
># container, that host's errors will be logged there and not here.
>#
>ErrorLog logs/error.log
>
>#
># LogLevel: Control the number of messages logged to the error.log.
># Possible values include: debug, info, notice, warn, error, crit,
># alert, emerg.
>#
>LogLevel warn
>
>#
># The following directives define some format nicknames for use with
># a CustomLog directive (see below).
>#
>LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
>LogFormat "%h %l %u %t \"%r\" %>s %b" common
>LogFormat "%{Referer}i -> %U" referer
>LogFormat "%{User-agent}i" agent
>
># You need to enable mod_logio.c to use %I and %O
>#LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
>
>#
># The location and format of the access logfile (Common Logfile Format).
># If you do not define any access logfiles within a <VirtualHost>
># container, they will be logged here. Contrariwise, if you *do*
># define per-<VirtualHost> access logfiles, transactions will be
># logged therein and *not* in this file.
>#
>CustomLog logs/access.log common
>
>#
># If you would like to have agent and referer logfiles, uncomment the
># following directives.
>#
>#CustomLog logs/referer.log referer
>#CustomLog logs/agent.log agent
>
>#
># If you prefer a single logfile with access, agent, and referer information
># (Combined Logfile Format) you can use the following directive.
>#
>#CustomLog logs/access.log combined
>
>#
># ServerTokens
># This directive configures what you return as the Server HTTP response
># Header. The default is 'Full' which sends information about the OS-Type
># and compiled in modules.
># Set to one of: Full | OS | Minor | Minimal | Major | Prod
># where Full conveys the most information, and Prod the least.
>#
>ServerTokens Full
>
>#
># Optionally add a line containing the server version and virtual host
># name to server-generated pages (internal error documents, FTP directory
># listings, mod_status and mod_info output etc., but not CGI generated
># documents or custom error documents).
># Set to "EMail" to also include a mailto: link to the ServerAdmin.
># Set to one of: On | Off | EMail
>#
>ServerSignature On
>
>#
># Aliases: Add here as many aliases as you need (with no limit). The format is
># Alias fakename realname
>#
># Note that if you include a trailing / on fakename then the server will
># require it to be present in the URL. So "/icons" isn't aliased in this
># example, only "/icons/". If the fakename is slash-terminated, then the
># realname must also be slash terminated, and if the fakename omits the
># trailing slash, the realname must also omit it.
>#
># We include the /icons/ alias for FancyIndexed directory listings. If you
># do not use FancyIndexing, you may comment this out.
>#
>Alias /icons/ "C:/Program Files/Apache Group/Apache2/icons/"
>
><Directory "C:/Program Files/Apache Group/Apache2/icons">
> Options Indexes MultiViews
> AllowOverride None
> Order allow,deny
> Allow from all
></Directory>
>
>#
># This should be changed to the ServerRoot/manual/. The alias provides
># the manual, even if you choose to move your DocumentRoot. You may comment
># this out if you do not care for the documentation.
>#
>AliasMatch ^/manual(?:/(?:de|en|es|fr|ja|ko|ru))?(/.*)?$ "C:/Program Files/Apache Group/Apache2/manual$1"
>
><Directory "C:/Program Files/Apache Group/Apache2/manual">
> Options Indexes
> AllowOverride None
> Order allow,deny
> Allow from all
>
> <Files *.html>
> SetHandler type-map
> </Files>
>
> SetEnvIf Request_URI ^/manual/(de|en|es|fr|ja|ko|ru)/ prefer-language=$1
> RedirectMatch 301 ^/manual(?:/(de|en|es|fr|ja|ko|ru)){2,}(/.*)?$ /manual/$1$2
></Directory>
>
>#
># ScriptAlias: This controls which directories contain server scripts.
># ScriptAliases are essentially the same as Aliases, except that
># documents in the realname directory are treated as applications and
># run by the server when requested rather than as documents sent to the client.
># The same rules about trailing "/" apply to ScriptAlias directives as to
># Alias.
>#
>ScriptAlias /cgi-bin/ "C:/Program Files/Apache Group/Apache2/cgi-bin/"
>ScriptAlias /php/ "C:/php-4.4.4-Win32/"
>
>#
># "C:/Program Files/Apache Group/Apache2/cgi-bin" should be changed to whatever your ScriptAliased
># CGI directory exists, if you have that configured.
>#
><Directory "C:/Program Files/Apache Group/Apache2/cgi-bin">
> AllowOverride All
> Options All
> Order allow,deny
> Allow from all
></Directory>
>
>#
># Redirect allows you to tell clients about documents which used to exist in
># your server's namespace, but do not anymore. This allows you to tell the
># clients where to look for the relocated document.
># Example:
># Redirect permanent /foo http://www.example.com/bar
>
>#
># Directives controlling the display of server-generated directory listings.
>#
>
>#
># IndexOptions: Controls the appearance of server-generated directory
># listings.
>#
>IndexOptions FancyIndexing VersionSort
>
>#
># AddIcon* directives tell the server which icon to show for different
># files or filename extensions. These are only displayed for
># FancyIndexed directories.
>#
>AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip
>
>AddIconByType (TXT,/icons/text.gif) text/*
>AddIconByType (IMG,/icons/image2.gif) image/*
>AddIconByType (SND,/icons/sound2.gif) audio/*
>AddIconByType (VID,/icons/movie.gif) video/*
>
>AddIcon /icons/binary.gif .bin .exe
>AddIcon /icons/binhex.gif .hqx
>AddIcon /icons/tar.gif .tar
>AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
>AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
>AddIcon /icons/a.gif .ps .ai .eps
>AddIcon /icons/layout.gif .html .shtml .htm .pdf
>AddIcon /icons/text.gif .txt
>AddIcon /icons/c.gif .c
>AddIcon /icons/p.gif .pl .py
>AddIcon /icons/f.gif .for
>AddIcon /icons/dvi.gif .dvi
>AddIcon /icons/uuencoded.gif .uu
>AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
>AddIcon /icons/tex.gif .tex
>AddIcon /icons/bomb.gif core
>
>AddIcon /icons/back.gif ..
>AddIcon /icons/hand.right.gif README
>AddIcon /icons/folder.gif ^^DIRECTORY^^
>AddIcon /icons/blank.gif ^^BLANKICON^^
>
>#
># DefaultIcon is which icon to show for files which do not have an icon
># explicitly set.
>#
>DefaultIcon /icons/unknown.gif
>
>#
># AddDescription allows you to place a short description after a file in
># server-generated indexes. These are only displayed for FancyIndexed
># directories.
># Format: AddDescription "description" filename
>#
>#AddDescription "GZIP compressed document" .gz
>#AddDescription "tar archive" .tar
>#AddDescription "GZIP compressed tar archive" .tgz
>
>#
># ReadmeName is the name of the README file the server will look for by
># default, and append to directory listings.
>#
># HeaderName is the name of a file which should be prepended to
># directory indexes.
>ReadmeName README.html
>HeaderName HEADER.html
>
>#
># IndexIgnore is a set of filenames which directory indexing should ignore
># and not include in the listing. Shell-style wildcarding is permitted.
>#
>IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t
>
>#
># DefaultLanguage and AddLanguage allows you to specify the language of
># a document. You can then use content negotiation to give a browser a
># file in a language the user can understand.
>#
># Specify a default language. This means that all data
># going out without a specific language tag (see below) will
># be marked with this one. You probably do NOT want to set
># this unless you are sure it is correct for all cases.
>#
># * It is generally better to not mark a page as
># * being a certain language than marking it with the wrong
># * language!
>#
># DefaultLanguage nl
>#
># Note 1: The suffix does not have to be the same as the language
># keyword --- those with documents in Polish (whose net-standard
># language code is pl) may wish to use "AddLanguage pl .po" to
># avoid the ambiguity with the common suffix for perl scripts.
>#
># Note 2: The example entries below illustrate that in some cases
># the two character 'Language' abbreviation is not identical to
># the two character 'Country' code for its country,
># E.g. 'Danmark/dk' versus 'Danish/da'.
>#
># Note 3: In the case of 'ltz' we violate the RFC by using a three char
># specifier. There is 'work in progress' to fix this and get
># the reference data for rfc1766 cleaned up.
>#
># Catalan (ca) - Croatian (hr) - Czech (cs) - Danish (da) - Dutch (nl)
># English (en) - Esperanto (eo) - Estonian (et) - French (fr) - German (de)
># Greek-Modern (el) - Hebrew (he) - Italian (it) - Japanese (ja)
># Korean (ko) - Luxembourgeois* (ltz) - Norwegian Nynorsk (nn)
># Norwegian (no) - Polish (pl) - Portugese (pt)
># Brazilian Portuguese (pt-BR) - Russian (ru) - Swedish (sv)
># Simplified Chinese (zh-CN) - Spanish (es) - Traditional Chinese (zh-TW)
>#
>AddLanguage ca .ca
>AddLanguage cs .cz .cs
>AddLanguage da .dk
>AddLanguage de .de
>AddLanguage el .el
>AddLanguage en .en
>AddLanguage eo .eo
>AddLanguage es .es
>AddLanguage et .et
>AddLanguage fr .fr
>AddLanguage he .he
>AddLanguage hr .hr
>AddLanguage it .it
>AddLanguage ja .ja
>AddLanguage ko .ko
>AddLanguage ltz .ltz
>AddLanguage nl .nl
>AddLanguage nn .nn
>AddLanguage no .no
>AddLanguage pl .po
>AddLanguage pt .pt
>AddLanguage pt-BR .pt-br
>AddLanguage ru .ru
>AddLanguage sv .sv
>AddLanguage zh-CN .zh-cn
>AddLanguage zh-TW .zh-tw
>
>#
># LanguagePriority allows you to give precedence to some languages
># in case of a tie during content negotiation.
>#
># Just list the languages in decreasing order of preference. We have
># more or less alphabetized them here. You probably want to change this.
>#
>LanguagePriority en ca cs da de el eo es et fr he hr it ja ko ltz nl nn no pl pt pt-BR ru sv zh-CN zh-TW
>
>#
># ForceLanguagePriority allows you to serve a result page rather than
># MULTIPLE CHOICES (Prefer) [in case of a tie] or NOT ACCEPTABLE (Fallback)
># [in case no accepted languages matched the available variants]
>#
>ForceLanguagePriority Prefer Fallback
>
>#
># Commonly used filename extensions to character sets. You probably
># want to avoid clashes with the language extensions, unless you
># are good at carefully testing your setup after each change.
># See http://www.iana.org/assignments/character-sets for the
># official list of charset names and their respective RFCs.
>#
>AddCharset ISO-8859-1 .iso8859-1 .latin1
>AddCharset ISO-8859-2 .iso8859-2 .latin2 .cen
>AddCharset ISO-8859-3 .iso8859-3 .latin3
>AddCharset ISO-8859-4 .iso8859-4 .latin4
>AddCharset ISO-8859-5 .iso8859-5 .latin5 .cyr .iso-ru
>AddCharset ISO-8859-6 .iso8859-6 .latin6 .arb
>AddCharset ISO-8859-7 .iso8859-7 .latin7 .grk
>AddCharset ISO-8859-8 .iso8859-8 .latin8 .heb
>AddCharset ISO-8859-9 .iso8859-9 .latin9 .trk
>AddCharset ISO-2022-JP .iso2022-jp .jis
>AddCharset ISO-2022-KR .iso2022-kr .kis
>AddCharset ISO-2022-CN .iso2022-cn .cis
>AddCharset Big5 .Big5 .big5
># For russian, more than one charset is used (depends on client, mostly):
>AddCharset WINDOWS-1251 .cp-1251 .win-1251
>AddCharset CP866 .cp866
>AddCharset KOI8-r .koi8-r .koi8-ru
>AddCharset KOI8-ru .koi8-uk .ua
>AddCharset ISO-10646-UCS-2 .ucs2
>AddCharset ISO-10646-UCS-4 .ucs4
>AddCharset UTF-8 .utf8
>
># The set below does not map to a specific (iso) standard
># but works on a fairly wide range of browsers. Note that
># capitalization actually matters (it should not, but it
># does for some browsers).
>#
># See http://www.iana.org/assignments/character-sets
># for a list of sorts. But browsers support few.
>#
>AddCharset GB2312 .gb2312 .gb
>AddCharset utf-7 .utf7
>AddCharset utf-8 .utf8
>AddCharset big5 .big5 .b5
>AddCharset EUC-TW .euc-tw
>AddCharset EUC-JP .euc-jp
>AddCharset EUC-KR .euc-kr
>AddCharset shift_jis .sjis
>
>#
># AddType allows you to add to or override the MIME configuration
># file mime.types for specific file types.
>#
>#AddType application/x-tar .tgz
>#
># AddEncoding allows you to have certain browsers (Mosaic/X 2.1+) uncompress
># information on the fly. Note: Not all browsers support this.
># Despite the name similarity, the following Add* directives have nothing
># to do with the FancyIndexing customization directives above.
>#
>#AddEncoding x-compress .Z
>#AddEncoding x-gzip .gz .tgz
>#
># If the AddEncoding directives above are commented-out, then you
># probably should define those extensions to indicate media types:
>#
>AddType application/x-compress .Z
>AddType application/x-gzip .gz .tgz
>
>AddType application/x-httpd-php .php
>
>#
># AddHandler allows you to map certain file extensions to "handlers":
># actions unrelated to filetype. These can be either built into the server
># or added with the Action directive (see below)
>#
># To use CGI scripts outside of ScriptAliased directories:
># (You will also need to add "ExecCGI" to the "Options" directive.)
>#
>AddHandler cgi-script .cgi .pl
>
>#
># For files that include their own HTTP headers:
>#
>#AddHandler send-as-is asis
>
>#
># For server-parsed imagemap files:
>#
>#AddHandler imap-file map
>
>#
># For type maps (negotiated resources):
># (This is enabled by default to allow the Apache "It Worked" page
># to be distributed in multiple languages.)
>#
>AddHandler type-map var
>
>#
># Filters allow you to process content before it is sent to the client.
>#
># To parse .shtml files for server-side includes (SSI):
># (You will also need to add "Includes" to the "Options" directive.)
>#
>#AddType text/html .shtml
>#AddOutputFilter INCLUDES .shtml
>
>#
># Action lets you define media types that will execute a script whenever
># a matching file is called. This eliminates the need for repeated URL
># pathnames for oft-used CGI file processors.
># Format: Action media/type /cgi-script/location
># Format: Action handler-name /cgi-script/location
>#
>Action application/x-httpd-php "/php/php.exe"
>
>#
># Customizable error responses come in three flavors:
># 1) plain text 2) local redirects 3) external redirects
>#
># Some examples:
>#ErrorDocument 500 "The server made a boo boo."
>#ErrorDocument 404 /missing.html
>#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
>#ErrorDocument 402 http://www.example.com/subscription_info.html
>#
>
>#
># Putting this all together, we can internationalize error responses.
>#
># We use Alias to redirect any /error/HTTP_<error>.html.var response to
># our collection of by-error message multi-language collections. We use
># includes to substitute the appropriate text.
>#
># You can modify the messages' appearance without changing any of the
># default HTTP_<error>.html.var files by adding the line:
>#
># Alias /error/include/ "/your/include/path/"
>#
># which allows you to create your own set of files by starting with the
># @exp_errordir@/include/ files and copying them to /your/include/path/,
># even on a per-VirtualHost basis. The default include files will display
># your Apache version number and your ServerAdmin email address regardless
># of the setting of ServerSignature.
>#
># The internationalized error documents require mod_alias, mod_include
># and mod_negotiation. To activate them, uncomment the following 30 lines.
>
># Alias /error/ "@exp_errordir@/"
>#
># <Directory "@exp_errordir@">
># AllowOverride None
># Options IncludesNoExec
># AddOutputFilter Includes html
># AddHandler type-map var
># Order allow,deny
># Allow from all
># LanguagePriority en cs de es fr it ja ko nl pl pt-br ro sv tr
># ForceLanguagePriority Prefer Fallback
># </Directory>
>#
># ErrorDocument 400 /error/HTTP_BAD_REQUEST.html.var
># ErrorDocument 401 /error/HTTP_UNAUTHORIZED.html.var
># ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var
># ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var
># ErrorDocument 405 /error/HTTP_METHOD_NOT_ALLOWED.html.var
># ErrorDocument 408 /error/HTTP_REQUEST_TIME_OUT.html.var
># ErrorDocument 410 /error/HTTP_GONE.html.var
># ErrorDocument 411 /error/HTTP_LENGTH_REQUIRED.html.var
># ErrorDocument 412 /error/HTTP_PRECONDITION_FAILED.html.var
># ErrorDocument 413 /error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var
># ErrorDocument 414 /error/HTTP_REQUEST_URI_TOO_LARGE.html.var
># ErrorDocument 415 /error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var
># ErrorDocument 500 /error/HTTP_INTERNAL_SERVER_ERROR.html.var
># ErrorDocument 501 /error/HTTP_NOT_IMPLEMENTED.html.var
># ErrorDocument 502 /error/HTTP_BAD_GATEWAY.html.var
># ErrorDocument 503 /error/HTTP_SERVICE_UNAVAILABLE.html.var
># ErrorDocument 506 /error/HTTP_VARIANT_ALSO_VARIES.html.var
>
>
>
>#
># The following directives modify normal HTTP response behavior to
># handle known problems with browser implementations.
>#
>BrowserMatch "Mozilla/2" nokeepalive
>BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
>BrowserMatch "RealPlayer 4\.0" force-response-1.0
>BrowserMatch "Java/1\.0" force-response-1.0
>BrowserMatch "JDK/1\.0" force-response-1.0
>
>#
># The following directive disables redirects on non-GET requests for
># a directory that does not include the trailing slash. This fixes a
># problem with Microsoft WebFolders which does not appropriately handle
># redirects for folders with DAV methods.
># Same deal with Apple's DAV filesystem and Gnome VFS support for DAV.
>#
>BrowserMatch "Microsoft Data Access Internet Publishing Provider" redirect-carefully
>BrowserMatch "MS FrontPage" redirect-carefully
>BrowserMatch "^WebDrive" redirect-carefully
>BrowserMatch "^WebDAVFS/1.[0123]" redirect-carefully
>BrowserMatch "^gnome-vfs" redirect-carefully
>BrowserMatch "^XML Spy" redirect-carefully
>BrowserMatch "^Dreamweaver-WebDAV-SCM1" redirect-carefully
>
>#
># Allow server status reports generated by mod_status,
># with the URL of http://servername/server-status
># Change the ".128.189.138.12" to match your domain to enable.
>#
>#<Location /server-status>
># SetHandler server-status
># Order deny,allow
># Deny from all
># Allow from .128.189.138.12
>#</Location>
>
>#
># Allow remote server configuration reports, with the URL of
># http://servername/server-info (requires that mod_info.c be loaded).
># Change the ".128.189.138.12" to match your domain to enable.
>#
>#<Location /server-info>
># SetHandler server-info
># Order deny,allow
># Deny from all
># Allow from .128.189.138.12
>#</Location>
>
>
>#
># Bring in additional module-specific configurations
>#
><IfModule mod_ssl.c>
> Include conf/ssl.conf
></IfModule>
>
>
>### Section 3: Virtual Hosts
>#
># VirtualHost: If you want to maintain multiple domains/hostnames on your
># machine you can setup VirtualHost containers for them. Most configurations
># use only name-based virtual hosts so the server doesn't need to worry about
># IP addresses. This is indicated by the asterisks in the directives below.
>#
># Please see the documentation at
># <URL:http://httpd.apache.org/docs/2.0/vhosts/>
># for further details before you try to setup virtual hosts.
>#
># You may use the command line option '-S' to verify your virtual host
># configuration.
>
>#
># Use name-based virtual hosting.
>#
>#NameVirtualHost *:80
>
>#
># VirtualHost example:
># Almost any Apache directive may go into a VirtualHost container.
># The first VirtualHost section is used for requests without a known
># server name.
>#
>#<VirtualHost *:80>
># ServerAdmin webmaster@dummy-host.example.com
># DocumentRoot /www/docs/dummy-host.example.com
># ServerName dummy-host.example.com
># ErrorLog logs/dummy-host.example.com-error_log
># CustomLog logs/dummy-host.example.com-access_log common
>#</VirtualHost>
>
># This part is to configure Apache Cache, especially for Expires module.
>#ExpiresActive On
>
>#ExpiresByType image/gif A2592000
>#ExpiresByType text/* "access plus 1 hour"
>#ExpiresByType text/xml "access plus 1 hour"
>
>MaxKeepAliveRequests 10000
><IfModule mpm_winnt.c>
> ThreadsPerChild 1900
> MaxRequestsPerChild 10000
></IfModule>
>
>LoadModule cache_module modules/mod_cache.so
>
><IfModule mod_cache.c>
> CacheForceCompletion 100
> CacheDefaultEXPire 3600
> CacheMaxExpire 86400
> #CacheIgnoreNoLastMod On
> CacheIgnoreCacheControl On
> #CacheLastModifiedFactor 0.1
>
> LoadModule disk_cache_module modules/mod_disk_cache.so
>
> <IfModule mod_disk_cache.c>
> CacheEnable disk /
> CacheRoot c:/cacheroot
> CacheSize 327680
> CacheDirLength 4
> CacheDirLevels 5
> CacheGcInterval 4
> </IfModule>
>
> #LoadModule mem_cache_module modules/mod_mem_cache.so
> <IfModule mod_mem_cache.c>
> CacheEnable mem /
> MCacheSize 8192
> MCacheMaxObjectCount 10000
> MCacheMinObjectSize 1
> MCacheMaxObjectSize 51200
> </IfModule>
></IfModule>
>
>
>
Re: Questions on modules to provide cache functions for Apache
Posted by Erica Zhang <er...@cs.ubc.ca>.
OK. For javascript file, I could find the files of Header and Data under
the directory of mod_disk_cache. For php file, I could not find it. To
enable you to get more details, you could access the simple application
by yourself through http://128.189.138.12 (I am not sure if you could
access it.) Also, I attach my http.conf, clienthint.js and gethint.php
to this email.
I really do not know why it could not work. BTW: I deploy the Apache
server on the Windows XP.
Regards,
Erica
David Wortham wrote:
> Erica,
> I'm out of ideas. I get the feeling that there's something you aren't
> telling us, but I feel that we have checked all the obvious points.
>
> I mis-typed the module name. I meant mod_disk_cache when I said
> mod_file_cache.
>
> Dave
>
>
>
>
>
> On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>
>>
>> David,
>>
>> 1) I tried /gethint.php without any GET/POST parameters. I got nothing
>> and it could not be cached even with force-caching directive. I do the
>> same thing for clienthint.js. It could work and display the source code
>> and could be cached.
>>
>> 2), The first part is the responses for clienthint.js:
>>
>> HTTP/1.x 200 OK
>> Date: Wed, 07 Mar 2007 00:05:08 GMT
>> Server: Apache/2.0.59 (Win32)
>> Last-Modified: Tue, 06 Mar 2007 01:57:50 GMT
>> *Etag: "88a26cc0-3ed-66b16380"*
>> *Accept-Ranges: bytes
>> Content-Length: 1005*
>> Keep-Alive: timeout=15, max=9999
>> Connection: Keep-Alive
>> *Content-Type: application/x-javascript*
>>
>> The second part is the response for gethint.php:
>>
>> HTTP/1.x 200 OK
>> Date: Wed, 07 Mar 2007 00:06:12 GMT
>> Server: Apache/2.0.59 (Win32)
>> X-Powered-By: PHP/4.4.4
>> Cache-Control: public
>> *Expires: Wed, 07 Mar 2007 00:16:12 GMT*
>> Last-Modified: Wed, 07 Mar 2007 00:06:12 GMT
>> Keep-Alive: timeout=15, max=10000
>> Connection: Keep-Alive
>> *Transfer-Encoding: chunked
>> Content-Type: text/html*
>>
>> I make the different header parts in bold.
>>
>> 3) Do you think I need to use mod_file_cache ? I do not use it.
>>
>> Regards,
>>
>> Erica
>>
>>
>> David Wortham wrote:
>>
>> > Erica,
>> > My only comments: either
>> > (1) the request parameters are killing mod_cache's desire to cache the
>> > file
>> > or
>> > (2) something is different in the headers between your JavaScript and
>> PHP
>> > responses.
>> >
>> > I would:
>> > (1) Try requesting /gethint.php without any GET/POST parameters (your
>> app
>> > should respond with correctly formatted XML [probably returning an
>> error
>> > code]). Is this file cached (with/without the force-caching
>> directive)?
>> > (2) Compare the javascript and xml response headers and compare any
>> > differences. I would think forcing mod_cache to ignore all headers
>> would
>> > make this trivial... but this may reveal something which may be
>> missing.
>> > (3) Clear your cache directory and see if your XML response creates a
>> > file,
>> > then check if your javascript file creates a cache file (assuming you
>> are
>> > still using mod_file_cache)
>> >
>> > Regards,
>> > Dave
>> >
>> >
>> > On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>> >
>> >>
>> >> Yes. I changed the PHP script. Now I change them back and also set
>> >> CacheIgnoreCacheControl On. And still could not work. For other
>> >> questions, please see the my answers below. Thanks.
>> >>
>> >> David Wortham wrote:
>> >>
>> >> > Erica,
>> >> > My observations of your headers:
>> >> > (1) The "Last-Modified" line contains the current timestamp (as
>> >> expected)
>> >>
>> >> After I set CacheIgnoreCacheControl On, it does not matter. Right ?
>> >> Although I move the headers to the top code, it still could not work.
>> >>
>> >> > (2) Your original question showed that you inserted an "Expires:"
>> >> header,
>> >> > but it doesn't show in your response. Did you change your PHP
>> script
>> >> > code
>> >> > since you asked the original question this morning?
>> >>
>> >> Yes. It is my fault.
>> >>
>> >> > (3) Are you returning XML or HTML? My experience with
>> >> XMLHttpResponse(s)
>> >> > required changing the content-type to "text/xml" (not really the
>> issue
>> >> at
>> >> > hand)
>> >> >
>> >> Does it matter ?
>> >>
>> >> > When you said that you got mod_cache to cache a JavaScript file,
>> was
>> >> > it in
>> >> > the same directory (and covered by the same mod_cache directives)?
>> >>
>> >> Yes, both javascript file and the php file are under htdocs
>> directory.
>> >>
>> >> >
>> >> > Did you try using the
>> >> > CacheIgnoreCacheControl On
>> >> > directive? Did it force the file to cache?
>> >>
>> >> I tried. But it could not work.
>> >>
>> >> >
>> >> > Regards,
>> >> > Dave
>> >> >
>> >> >
>> >> > On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>> >> >
>> >> >>
>> >> >> I use live http headers to catch the headers. I listed them below.
>> >> Well
>> >> >> I found that php file has not been given the http headers. So is
>> this
>> >> >> the problem for not caching the response produced by it ? Then how
>> >> can
>> >> I
>> >> >> handle this problem ? Also, is there some mod_cache log that I
>> could
>> >> >> refer ? Thanks.
>> >> >>
>> >> >> http://128.189.246.64/gethint.php?q=Eric&sid=0.11837499670287688
>> >> >>
>> >> >> GET /gethint.php?q=Eric&sid=0.11837499670287688 HTTP/1.1
>> >> >> Host: 128.189.246.64
>> >> >> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>> >> rv:1.8.1.2)
>> >> >> Gecko/20070219 Firefox/2.0.0.2
>> >> >> Accept:
>> >> >> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9
>> >> >> ,text/plain;q=0.8,image/png,*/*;q=0.5
>> >> >> Accept-Language: en-us,en;q=0.5
>> >> >> Accept-Encoding: gzip,deflate
>> >> >> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>> >> >> Keep-Alive: 300
>> >> >> Connection: keep-alive
>> >> >> Referer: http://128.189.246.64/
>> >> >>
>> >> >> HTTP/1.x 200 OK
>> >> >> Date: Tue, 06 Mar 2007 22:35:34 GMT
>> >> >> Server: Apache/2.0.59 (Win32)
>> >> >> X-Powered-By: PHP/4.4.4
>> >> >> Cache-Control: public
>> >> >> Last-Modified: Tue, 06 Mar 2007 22:35:34 GMT
>> >> >> Keep-Alive: timeout=15, max=10000
>> >> >> Connection: Keep-Alive
>> >> >> Transfer-Encoding: chunked
>> >> >> Content-Type: text/html
>> >> >>
>> >> >>
>> >> >> Erica Zhang wrote:
>> >> >>
>> >> >> > Well, even I use the blinding-cache. It still could not work.
>> >> Thanks,
>> >> >> >
>> >> >> > Erica
>> >> >> >
>> >> >> > David Wortham wrote:
>> >> >> >
>> >> >> >> Erica,
>> >> >> >> I'm not sure why mod_cache should not be able to work
>> (assuming
>> >> >> your
>> >> >> >> module and pages are configured correctly).
>> >> >> >>
>> >> >> >> IIRC, JavaScript is used on the presentation request (with
>> the
>> >> >> >> webpage),
>> >> >> >> whereas the XMLHttpRequest response is a PHP-generated XML
>> >> document.
>> >> >> >> Perhaps your extension ('.php" maybe?) or the mime/content-type
>> >> >> >> ("text/xml")
>> >> >> >> is what is causing mod_cache to skip the file?
>> >> >> >>
>> >> >> >> Also, from what I can gather, using mod_cache with mod_proxy
>> >> (as a
>> >> >> >> caching proxy) can alter the effects of mod_cache slightly.
>> >> You may
>> >> >> >> want to
>> >> >> >> read up on that.
>> >> >> >>
>> >> >> >> Try using the following directive with mod_cache:
>> >> >> >> CacheIgnoreNoLastMod On
>> >> >> >>
>> >> >> >> see:
>> >> >> >>
>> >> >>
>> >>
>> http://webauth.stanford.edu/manual/mod/mod_cache.html#CacheIgnoreNoLastMod
>>
>> >>
>> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> This apparently forces blind-caching which Joe suggests is
>> bad (I
>> >> >> >> don't know
>> >> >> >> anything about it). Short of that, you just need to read the
>> >> >> mod_cache
>> >> >> >> manual and make sure your XML response contains the necessary
>> >> headers
>> >> >> >> to get
>> >> >> >> mod_cache to work correctly.
>> >> >> >>
>> >> >> >> Regards,
>> >> >> >> Dave
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>> >> >> >>
>> >> >> >>>
>> >> >> >>> No, still not work. Infact, mod_cache could work, because it
>> >> could
>> >> >> >>> cache
>> >> >> >>> the javascript. But it could not work for dynamic HTTP
>> responses
>> >> >> >>> responding to XMLHttpRequests in Ajax technology. So I suspect
>> >> >> >>> mod_cache
>> >> >> >>> could not support this function. And I need provide such
>> function
>> >> by
>> >> >> >>> myself. I prefer to do it in Apache, a comparatively
>> general way
>> >> >> >>> instead
>> >> >> >>> of application itself.
>> >> >> >>>
>> >> >> >>>
>> >> >> >>> Erica
>> >> >> >>>
>> >> >> >>> Joachim Zobel wrote:
>> >> >> >>>
>> >> >> >>> >Am Montag, den 05.03.2007, 22:53 -0800 schrieb Erica Zhang:
>> >> >> >>> >
>> >> >> >>> >
>> >> >> >>> >>header("Cache-Control: public"); // HTTP/1.1
>> >> >> >>> >>header("Expires: " .gmdate ("D, d M Y H:i:s", time() + 60 *
>> >> 10).
>> >> "
>> >> >> >>> GMT");
>> >> >> >>> >>header( "Last-Modified: " .gmdate( 'D, d M Y H:i:s' ). "
>> >> GMT" );
>> >> >> >>> >>echo $response;
>> >> >> >>> >>
>> >> >> >>> >>
>> >> >> >>> >
>> >> >> >>> >I am not shure about mod_caches behaviour, but omitting
>> >> >> >>> last-modified is
>> >> >> >>> >worth a try.
>> >> >> >>> >
>> >> >> >>> >Sincerely,
>> >> >> >>> >Joachim
>> >> >> >>> >
>> >> >> >>> >
>> >> >> >>> >
>> >> >> >>>
>> >> >> >>>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>> >
>>
>>
>
Re: Questions on modules to provide cache functions for Apache
Posted by David Wortham <dj...@gmail.com>.
Erica,
I'm out of ideas. I get the feeling that there's something you aren't
telling us, but I feel that we have checked all the obvious points.
I mis-typed the module name. I meant mod_disk_cache when I said
mod_file_cache.
Dave
On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>
> David,
>
> 1) I tried /gethint.php without any GET/POST parameters. I got nothing
> and it could not be cached even with force-caching directive. I do the
> same thing for clienthint.js. It could work and display the source code
> and could be cached.
>
> 2), The first part is the responses for clienthint.js:
>
> HTTP/1.x 200 OK
> Date: Wed, 07 Mar 2007 00:05:08 GMT
> Server: Apache/2.0.59 (Win32)
> Last-Modified: Tue, 06 Mar 2007 01:57:50 GMT
> *Etag: "88a26cc0-3ed-66b16380"*
> *Accept-Ranges: bytes
> Content-Length: 1005*
> Keep-Alive: timeout=15, max=9999
> Connection: Keep-Alive
> *Content-Type: application/x-javascript*
>
> The second part is the response for gethint.php:
>
> HTTP/1.x 200 OK
> Date: Wed, 07 Mar 2007 00:06:12 GMT
> Server: Apache/2.0.59 (Win32)
> X-Powered-By: PHP/4.4.4
> Cache-Control: public
> *Expires: Wed, 07 Mar 2007 00:16:12 GMT*
> Last-Modified: Wed, 07 Mar 2007 00:06:12 GMT
> Keep-Alive: timeout=15, max=10000
> Connection: Keep-Alive
> *Transfer-Encoding: chunked
> Content-Type: text/html*
>
> I make the different header parts in bold.
>
> 3) Do you think I need to use mod_file_cache ? I do not use it.
>
> Regards,
>
> Erica
>
>
> David Wortham wrote:
>
> > Erica,
> > My only comments: either
> > (1) the request parameters are killing mod_cache's desire to cache the
> > file
> > or
> > (2) something is different in the headers between your JavaScript and
> PHP
> > responses.
> >
> > I would:
> > (1) Try requesting /gethint.php without any GET/POST parameters (your
> app
> > should respond with correctly formatted XML [probably returning an error
> > code]). Is this file cached (with/without the force-caching directive)?
> > (2) Compare the javascript and xml response headers and compare any
> > differences. I would think forcing mod_cache to ignore all headers
> would
> > make this trivial... but this may reveal something which may be missing.
> > (3) Clear your cache directory and see if your XML response creates a
> > file,
> > then check if your javascript file creates a cache file (assuming you
> are
> > still using mod_file_cache)
> >
> > Regards,
> > Dave
> >
> >
> > On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
> >
> >>
> >> Yes. I changed the PHP script. Now I change them back and also set
> >> CacheIgnoreCacheControl On. And still could not work. For other
> >> questions, please see the my answers below. Thanks.
> >>
> >> David Wortham wrote:
> >>
> >> > Erica,
> >> > My observations of your headers:
> >> > (1) The "Last-Modified" line contains the current timestamp (as
> >> expected)
> >>
> >> After I set CacheIgnoreCacheControl On, it does not matter. Right ?
> >> Although I move the headers to the top code, it still could not work.
> >>
> >> > (2) Your original question showed that you inserted an "Expires:"
> >> header,
> >> > but it doesn't show in your response. Did you change your PHP script
> >> > code
> >> > since you asked the original question this morning?
> >>
> >> Yes. It is my fault.
> >>
> >> > (3) Are you returning XML or HTML? My experience with
> >> XMLHttpResponse(s)
> >> > required changing the content-type to "text/xml" (not really the
> issue
> >> at
> >> > hand)
> >> >
> >> Does it matter ?
> >>
> >> > When you said that you got mod_cache to cache a JavaScript file, was
> >> > it in
> >> > the same directory (and covered by the same mod_cache directives)?
> >>
> >> Yes, both javascript file and the php file are under htdocs directory.
> >>
> >> >
> >> > Did you try using the
> >> > CacheIgnoreCacheControl On
> >> > directive? Did it force the file to cache?
> >>
> >> I tried. But it could not work.
> >>
> >> >
> >> > Regards,
> >> > Dave
> >> >
> >> >
> >> > On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
> >> >
> >> >>
> >> >> I use live http headers to catch the headers. I listed them below.
> >> Well
> >> >> I found that php file has not been given the http headers. So is
> this
> >> >> the problem for not caching the response produced by it ? Then how
> >> can
> >> I
> >> >> handle this problem ? Also, is there some mod_cache log that I could
> >> >> refer ? Thanks.
> >> >>
> >> >> http://128.189.246.64/gethint.php?q=Eric&sid=0.11837499670287688
> >> >>
> >> >> GET /gethint.php?q=Eric&sid=0.11837499670287688 HTTP/1.1
> >> >> Host: 128.189.246.64
> >> >> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
> >> rv:1.8.1.2)
> >> >> Gecko/20070219 Firefox/2.0.0.2
> >> >> Accept:
> >> >> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9
> >> >> ,text/plain;q=0.8,image/png,*/*;q=0.5
> >> >> Accept-Language: en-us,en;q=0.5
> >> >> Accept-Encoding: gzip,deflate
> >> >> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> >> >> Keep-Alive: 300
> >> >> Connection: keep-alive
> >> >> Referer: http://128.189.246.64/
> >> >>
> >> >> HTTP/1.x 200 OK
> >> >> Date: Tue, 06 Mar 2007 22:35:34 GMT
> >> >> Server: Apache/2.0.59 (Win32)
> >> >> X-Powered-By: PHP/4.4.4
> >> >> Cache-Control: public
> >> >> Last-Modified: Tue, 06 Mar 2007 22:35:34 GMT
> >> >> Keep-Alive: timeout=15, max=10000
> >> >> Connection: Keep-Alive
> >> >> Transfer-Encoding: chunked
> >> >> Content-Type: text/html
> >> >>
> >> >>
> >> >> Erica Zhang wrote:
> >> >>
> >> >> > Well, even I use the blinding-cache. It still could not work.
> >> Thanks,
> >> >> >
> >> >> > Erica
> >> >> >
> >> >> > David Wortham wrote:
> >> >> >
> >> >> >> Erica,
> >> >> >> I'm not sure why mod_cache should not be able to work (assuming
> >> >> your
> >> >> >> module and pages are configured correctly).
> >> >> >>
> >> >> >> IIRC, JavaScript is used on the presentation request (with the
> >> >> >> webpage),
> >> >> >> whereas the XMLHttpRequest response is a PHP-generated XML
> >> document.
> >> >> >> Perhaps your extension ('.php" maybe?) or the mime/content-type
> >> >> >> ("text/xml")
> >> >> >> is what is causing mod_cache to skip the file?
> >> >> >>
> >> >> >> Also, from what I can gather, using mod_cache with mod_proxy
> >> (as a
> >> >> >> caching proxy) can alter the effects of mod_cache slightly.
> >> You may
> >> >> >> want to
> >> >> >> read up on that.
> >> >> >>
> >> >> >> Try using the following directive with mod_cache:
> >> >> >> CacheIgnoreNoLastMod On
> >> >> >>
> >> >> >> see:
> >> >> >>
> >> >>
> >>
> http://webauth.stanford.edu/manual/mod/mod_cache.html#CacheIgnoreNoLastMod
> >>
> >> >>
> >> >> >>
> >> >> >>
> >> >> >> This apparently forces blind-caching which Joe suggests is bad (I
> >> >> >> don't know
> >> >> >> anything about it). Short of that, you just need to read the
> >> >> mod_cache
> >> >> >> manual and make sure your XML response contains the necessary
> >> headers
> >> >> >> to get
> >> >> >> mod_cache to work correctly.
> >> >> >>
> >> >> >> Regards,
> >> >> >> Dave
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
> >> >> >>
> >> >> >>>
> >> >> >>> No, still not work. Infact, mod_cache could work, because it
> >> could
> >> >> >>> cache
> >> >> >>> the javascript. But it could not work for dynamic HTTP responses
> >> >> >>> responding to XMLHttpRequests in Ajax technology. So I suspect
> >> >> >>> mod_cache
> >> >> >>> could not support this function. And I need provide such
> function
> >> by
> >> >> >>> myself. I prefer to do it in Apache, a comparatively general way
> >> >> >>> instead
> >> >> >>> of application itself.
> >> >> >>>
> >> >> >>>
> >> >> >>> Erica
> >> >> >>>
> >> >> >>> Joachim Zobel wrote:
> >> >> >>>
> >> >> >>> >Am Montag, den 05.03.2007, 22:53 -0800 schrieb Erica Zhang:
> >> >> >>> >
> >> >> >>> >
> >> >> >>> >>header("Cache-Control: public"); // HTTP/1.1
> >> >> >>> >>header("Expires: " .gmdate ("D, d M Y H:i:s", time() + 60 *
> >> 10).
> >> "
> >> >> >>> GMT");
> >> >> >>> >>header( "Last-Modified: " .gmdate( 'D, d M Y H:i:s' ). "
> >> GMT" );
> >> >> >>> >>echo $response;
> >> >> >>> >>
> >> >> >>> >>
> >> >> >>> >
> >> >> >>> >I am not shure about mod_caches behaviour, but omitting
> >> >> >>> last-modified is
> >> >> >>> >worth a try.
> >> >> >>> >
> >> >> >>> >Sincerely,
> >> >> >>> >Joachim
> >> >> >>> >
> >> >> >>> >
> >> >> >>> >
> >> >> >>>
> >> >> >>>
> >> >> >>
> >> >>
> >> >>
> >> >
> >>
> >>
> >
>
>
Re: Questions on modules to provide cache functions for Apache
Posted by Issac Goldstand <ma...@beamartyr.net>.
Both responses look cachable. Not sure why mod_cache wouldn't be
caching them...
Erica Zhang wrote:
>
> 3) Do you think I need to use mod_file_cache ? I do not use it.
NO. mod_file_cache simply mmaps static files' filehandles, enabling
Apache to serve them much faster. The name is really misleading because
it's not really caching anything (except the filehandles), and IIRC
really doesn't have anything to do with the rest of the cache family of
modules. It'll boost performance for serving the static JS file, but
that's about it.
Issac
Re: Questions on modules to provide cache functions for Apache
Posted by Erica Zhang <er...@cs.ubc.ca>.
David,
1) I tried /gethint.php without any GET/POST parameters. I got nothing
and it could not be cached even with force-caching directive. I do the
same thing for clienthint.js. It could work and display the source code
and could be cached.
2), The first part is the responses for clienthint.js:
HTTP/1.x 200 OK
Date: Wed, 07 Mar 2007 00:05:08 GMT
Server: Apache/2.0.59 (Win32)
Last-Modified: Tue, 06 Mar 2007 01:57:50 GMT
*Etag: "88a26cc0-3ed-66b16380"*
*Accept-Ranges: bytes
Content-Length: 1005*
Keep-Alive: timeout=15, max=9999
Connection: Keep-Alive
*Content-Type: application/x-javascript*
The second part is the response for gethint.php:
HTTP/1.x 200 OK
Date: Wed, 07 Mar 2007 00:06:12 GMT
Server: Apache/2.0.59 (Win32)
X-Powered-By: PHP/4.4.4
Cache-Control: public
*Expires: Wed, 07 Mar 2007 00:16:12 GMT*
Last-Modified: Wed, 07 Mar 2007 00:06:12 GMT
Keep-Alive: timeout=15, max=10000
Connection: Keep-Alive
*Transfer-Encoding: chunked
Content-Type: text/html*
I make the different header parts in bold.
3) Do you think I need to use mod_file_cache ? I do not use it.
Regards,
Erica
David Wortham wrote:
> Erica,
> My only comments: either
> (1) the request parameters are killing mod_cache's desire to cache the
> file
> or
> (2) something is different in the headers between your JavaScript and PHP
> responses.
>
> I would:
> (1) Try requesting /gethint.php without any GET/POST parameters (your app
> should respond with correctly formatted XML [probably returning an error
> code]). Is this file cached (with/without the force-caching directive)?
> (2) Compare the javascript and xml response headers and compare any
> differences. I would think forcing mod_cache to ignore all headers would
> make this trivial... but this may reveal something which may be missing.
> (3) Clear your cache directory and see if your XML response creates a
> file,
> then check if your javascript file creates a cache file (assuming you are
> still using mod_file_cache)
>
> Regards,
> Dave
>
>
> On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>
>>
>> Yes. I changed the PHP script. Now I change them back and also set
>> CacheIgnoreCacheControl On. And still could not work. For other
>> questions, please see the my answers below. Thanks.
>>
>> David Wortham wrote:
>>
>> > Erica,
>> > My observations of your headers:
>> > (1) The "Last-Modified" line contains the current timestamp (as
>> expected)
>>
>> After I set CacheIgnoreCacheControl On, it does not matter. Right ?
>> Although I move the headers to the top code, it still could not work.
>>
>> > (2) Your original question showed that you inserted an "Expires:"
>> header,
>> > but it doesn't show in your response. Did you change your PHP script
>> > code
>> > since you asked the original question this morning?
>>
>> Yes. It is my fault.
>>
>> > (3) Are you returning XML or HTML? My experience with
>> XMLHttpResponse(s)
>> > required changing the content-type to "text/xml" (not really the issue
>> at
>> > hand)
>> >
>> Does it matter ?
>>
>> > When you said that you got mod_cache to cache a JavaScript file, was
>> > it in
>> > the same directory (and covered by the same mod_cache directives)?
>>
>> Yes, both javascript file and the php file are under htdocs directory.
>>
>> >
>> > Did you try using the
>> > CacheIgnoreCacheControl On
>> > directive? Did it force the file to cache?
>>
>> I tried. But it could not work.
>>
>> >
>> > Regards,
>> > Dave
>> >
>> >
>> > On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>> >
>> >>
>> >> I use live http headers to catch the headers. I listed them below.
>> Well
>> >> I found that php file has not been given the http headers. So is this
>> >> the problem for not caching the response produced by it ? Then how
>> can
>> I
>> >> handle this problem ? Also, is there some mod_cache log that I could
>> >> refer ? Thanks.
>> >>
>> >> http://128.189.246.64/gethint.php?q=Eric&sid=0.11837499670287688
>> >>
>> >> GET /gethint.php?q=Eric&sid=0.11837499670287688 HTTP/1.1
>> >> Host: 128.189.246.64
>> >> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>> rv:1.8.1.2)
>> >> Gecko/20070219 Firefox/2.0.0.2
>> >> Accept:
>> >> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9
>> >> ,text/plain;q=0.8,image/png,*/*;q=0.5
>> >> Accept-Language: en-us,en;q=0.5
>> >> Accept-Encoding: gzip,deflate
>> >> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>> >> Keep-Alive: 300
>> >> Connection: keep-alive
>> >> Referer: http://128.189.246.64/
>> >>
>> >> HTTP/1.x 200 OK
>> >> Date: Tue, 06 Mar 2007 22:35:34 GMT
>> >> Server: Apache/2.0.59 (Win32)
>> >> X-Powered-By: PHP/4.4.4
>> >> Cache-Control: public
>> >> Last-Modified: Tue, 06 Mar 2007 22:35:34 GMT
>> >> Keep-Alive: timeout=15, max=10000
>> >> Connection: Keep-Alive
>> >> Transfer-Encoding: chunked
>> >> Content-Type: text/html
>> >>
>> >>
>> >> Erica Zhang wrote:
>> >>
>> >> > Well, even I use the blinding-cache. It still could not work.
>> Thanks,
>> >> >
>> >> > Erica
>> >> >
>> >> > David Wortham wrote:
>> >> >
>> >> >> Erica,
>> >> >> I'm not sure why mod_cache should not be able to work (assuming
>> >> your
>> >> >> module and pages are configured correctly).
>> >> >>
>> >> >> IIRC, JavaScript is used on the presentation request (with the
>> >> >> webpage),
>> >> >> whereas the XMLHttpRequest response is a PHP-generated XML
>> document.
>> >> >> Perhaps your extension ('.php" maybe?) or the mime/content-type
>> >> >> ("text/xml")
>> >> >> is what is causing mod_cache to skip the file?
>> >> >>
>> >> >> Also, from what I can gather, using mod_cache with mod_proxy
>> (as a
>> >> >> caching proxy) can alter the effects of mod_cache slightly.
>> You may
>> >> >> want to
>> >> >> read up on that.
>> >> >>
>> >> >> Try using the following directive with mod_cache:
>> >> >> CacheIgnoreNoLastMod On
>> >> >>
>> >> >> see:
>> >> >>
>> >>
>> http://webauth.stanford.edu/manual/mod/mod_cache.html#CacheIgnoreNoLastMod
>>
>> >>
>> >> >>
>> >> >>
>> >> >> This apparently forces blind-caching which Joe suggests is bad (I
>> >> >> don't know
>> >> >> anything about it). Short of that, you just need to read the
>> >> mod_cache
>> >> >> manual and make sure your XML response contains the necessary
>> headers
>> >> >> to get
>> >> >> mod_cache to work correctly.
>> >> >>
>> >> >> Regards,
>> >> >> Dave
>> >> >>
>> >> >>
>> >> >>
>> >> >> On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>> >> >>
>> >> >>>
>> >> >>> No, still not work. Infact, mod_cache could work, because it
>> could
>> >> >>> cache
>> >> >>> the javascript. But it could not work for dynamic HTTP responses
>> >> >>> responding to XMLHttpRequests in Ajax technology. So I suspect
>> >> >>> mod_cache
>> >> >>> could not support this function. And I need provide such function
>> by
>> >> >>> myself. I prefer to do it in Apache, a comparatively general way
>> >> >>> instead
>> >> >>> of application itself.
>> >> >>>
>> >> >>>
>> >> >>> Erica
>> >> >>>
>> >> >>> Joachim Zobel wrote:
>> >> >>>
>> >> >>> >Am Montag, den 05.03.2007, 22:53 -0800 schrieb Erica Zhang:
>> >> >>> >
>> >> >>> >
>> >> >>> >>header("Cache-Control: public"); // HTTP/1.1
>> >> >>> >>header("Expires: " .gmdate ("D, d M Y H:i:s", time() + 60 *
>> 10).
>> "
>> >> >>> GMT");
>> >> >>> >>header( "Last-Modified: " .gmdate( 'D, d M Y H:i:s' ). "
>> GMT" );
>> >> >>> >>echo $response;
>> >> >>> >>
>> >> >>> >>
>> >> >>> >
>> >> >>> >I am not shure about mod_caches behaviour, but omitting
>> >> >>> last-modified is
>> >> >>> >worth a try.
>> >> >>> >
>> >> >>> >Sincerely,
>> >> >>> >Joachim
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>>
>> >> >>>
>> >> >>
>> >>
>> >>
>> >
>>
>>
>
Re: Questions on modules to provide cache functions for Apache
Posted by David Wortham <dj...@gmail.com>.
Erica,
My only comments: either
(1) the request parameters are killing mod_cache's desire to cache the file
or
(2) something is different in the headers between your JavaScript and PHP
responses.
I would:
(1) Try requesting /gethint.php without any GET/POST parameters (your app
should respond with correctly formatted XML [probably returning an error
code]). Is this file cached (with/without the force-caching directive)?
(2) Compare the javascript and xml response headers and compare any
differences. I would think forcing mod_cache to ignore all headers would
make this trivial... but this may reveal something which may be missing.
(3) Clear your cache directory and see if your XML response creates a file,
then check if your javascript file creates a cache file (assuming you are
still using mod_file_cache)
Regards,
Dave
On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>
> Yes. I changed the PHP script. Now I change them back and also set
> CacheIgnoreCacheControl On. And still could not work. For other
> questions, please see the my answers below. Thanks.
>
> David Wortham wrote:
>
> > Erica,
> > My observations of your headers:
> > (1) The "Last-Modified" line contains the current timestamp (as
> expected)
>
> After I set CacheIgnoreCacheControl On, it does not matter. Right ?
> Although I move the headers to the top code, it still could not work.
>
> > (2) Your original question showed that you inserted an "Expires:"
> header,
> > but it doesn't show in your response. Did you change your PHP script
> > code
> > since you asked the original question this morning?
>
> Yes. It is my fault.
>
> > (3) Are you returning XML or HTML? My experience with
> XMLHttpResponse(s)
> > required changing the content-type to "text/xml" (not really the issue
> at
> > hand)
> >
> Does it matter ?
>
> > When you said that you got mod_cache to cache a JavaScript file, was
> > it in
> > the same directory (and covered by the same mod_cache directives)?
>
> Yes, both javascript file and the php file are under htdocs directory.
>
> >
> > Did you try using the
> > CacheIgnoreCacheControl On
> > directive? Did it force the file to cache?
>
> I tried. But it could not work.
>
> >
> > Regards,
> > Dave
> >
> >
> > On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
> >
> >>
> >> I use live http headers to catch the headers. I listed them below. Well
> >> I found that php file has not been given the http headers. So is this
> >> the problem for not caching the response produced by it ? Then how can
> I
> >> handle this problem ? Also, is there some mod_cache log that I could
> >> refer ? Thanks.
> >>
> >> http://128.189.246.64/gethint.php?q=Eric&sid=0.11837499670287688
> >>
> >> GET /gethint.php?q=Eric&sid=0.11837499670287688 HTTP/1.1
> >> Host: 128.189.246.64
> >> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2)
> >> Gecko/20070219 Firefox/2.0.0.2
> >> Accept:
> >> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9
> >> ,text/plain;q=0.8,image/png,*/*;q=0.5
> >> Accept-Language: en-us,en;q=0.5
> >> Accept-Encoding: gzip,deflate
> >> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> >> Keep-Alive: 300
> >> Connection: keep-alive
> >> Referer: http://128.189.246.64/
> >>
> >> HTTP/1.x 200 OK
> >> Date: Tue, 06 Mar 2007 22:35:34 GMT
> >> Server: Apache/2.0.59 (Win32)
> >> X-Powered-By: PHP/4.4.4
> >> Cache-Control: public
> >> Last-Modified: Tue, 06 Mar 2007 22:35:34 GMT
> >> Keep-Alive: timeout=15, max=10000
> >> Connection: Keep-Alive
> >> Transfer-Encoding: chunked
> >> Content-Type: text/html
> >>
> >>
> >> Erica Zhang wrote:
> >>
> >> > Well, even I use the blinding-cache. It still could not work. Thanks,
> >> >
> >> > Erica
> >> >
> >> > David Wortham wrote:
> >> >
> >> >> Erica,
> >> >> I'm not sure why mod_cache should not be able to work (assuming
> >> your
> >> >> module and pages are configured correctly).
> >> >>
> >> >> IIRC, JavaScript is used on the presentation request (with the
> >> >> webpage),
> >> >> whereas the XMLHttpRequest response is a PHP-generated XML document.
> >> >> Perhaps your extension ('.php" maybe?) or the mime/content-type
> >> >> ("text/xml")
> >> >> is what is causing mod_cache to skip the file?
> >> >>
> >> >> Also, from what I can gather, using mod_cache with mod_proxy (as a
> >> >> caching proxy) can alter the effects of mod_cache slightly. You may
> >> >> want to
> >> >> read up on that.
> >> >>
> >> >> Try using the following directive with mod_cache:
> >> >> CacheIgnoreNoLastMod On
> >> >>
> >> >> see:
> >> >>
> >>
> http://webauth.stanford.edu/manual/mod/mod_cache.html#CacheIgnoreNoLastMod
> >>
> >> >>
> >> >>
> >> >> This apparently forces blind-caching which Joe suggests is bad (I
> >> >> don't know
> >> >> anything about it). Short of that, you just need to read the
> >> mod_cache
> >> >> manual and make sure your XML response contains the necessary
> headers
> >> >> to get
> >> >> mod_cache to work correctly.
> >> >>
> >> >> Regards,
> >> >> Dave
> >> >>
> >> >>
> >> >>
> >> >> On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
> >> >>
> >> >>>
> >> >>> No, still not work. Infact, mod_cache could work, because it could
> >> >>> cache
> >> >>> the javascript. But it could not work for dynamic HTTP responses
> >> >>> responding to XMLHttpRequests in Ajax technology. So I suspect
> >> >>> mod_cache
> >> >>> could not support this function. And I need provide such function
> by
> >> >>> myself. I prefer to do it in Apache, a comparatively general way
> >> >>> instead
> >> >>> of application itself.
> >> >>>
> >> >>>
> >> >>> Erica
> >> >>>
> >> >>> Joachim Zobel wrote:
> >> >>>
> >> >>> >Am Montag, den 05.03.2007, 22:53 -0800 schrieb Erica Zhang:
> >> >>> >
> >> >>> >
> >> >>> >>header("Cache-Control: public"); // HTTP/1.1
> >> >>> >>header("Expires: " .gmdate ("D, d M Y H:i:s", time() + 60 * 10).
> "
> >> >>> GMT");
> >> >>> >>header( "Last-Modified: " .gmdate( 'D, d M Y H:i:s' ). " GMT" );
> >> >>> >>echo $response;
> >> >>> >>
> >> >>> >>
> >> >>> >
> >> >>> >I am not shure about mod_caches behaviour, but omitting
> >> >>> last-modified is
> >> >>> >worth a try.
> >> >>> >
> >> >>> >Sincerely,
> >> >>> >Joachim
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>>
> >> >>>
> >> >>
> >>
> >>
> >
>
>
Re: Questions on modules to provide cache functions for Apache
Posted by Erica Zhang <er...@cs.ubc.ca>.
Yes. I changed the PHP script. Now I change them back and also set
CacheIgnoreCacheControl On. And still could not work. For other
questions, please see the my answers below. Thanks.
David Wortham wrote:
> Erica,
> My observations of your headers:
> (1) The "Last-Modified" line contains the current timestamp (as expected)
After I set CacheIgnoreCacheControl On, it does not matter. Right ?
Although I move the headers to the top code, it still could not work.
> (2) Your original question showed that you inserted an "Expires:" header,
> but it doesn't show in your response. Did you change your PHP script
> code
> since you asked the original question this morning?
Yes. It is my fault.
> (3) Are you returning XML or HTML? My experience with XMLHttpResponse(s)
> required changing the content-type to "text/xml" (not really the issue at
> hand)
>
Does it matter ?
> When you said that you got mod_cache to cache a JavaScript file, was
> it in
> the same directory (and covered by the same mod_cache directives)?
Yes, both javascript file and the php file are under htdocs directory.
>
> Did you try using the
> CacheIgnoreCacheControl On
> directive? Did it force the file to cache?
I tried. But it could not work.
>
> Regards,
> Dave
>
>
> On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>
>>
>> I use live http headers to catch the headers. I listed them below. Well
>> I found that php file has not been given the http headers. So is this
>> the problem for not caching the response produced by it ? Then how can I
>> handle this problem ? Also, is there some mod_cache log that I could
>> refer ? Thanks.
>>
>> http://128.189.246.64/gethint.php?q=Eric&sid=0.11837499670287688
>>
>> GET /gethint.php?q=Eric&sid=0.11837499670287688 HTTP/1.1
>> Host: 128.189.246.64
>> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2)
>> Gecko/20070219 Firefox/2.0.0.2
>> Accept:
>> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9
>> ,text/plain;q=0.8,image/png,*/*;q=0.5
>> Accept-Language: en-us,en;q=0.5
>> Accept-Encoding: gzip,deflate
>> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
>> Keep-Alive: 300
>> Connection: keep-alive
>> Referer: http://128.189.246.64/
>>
>> HTTP/1.x 200 OK
>> Date: Tue, 06 Mar 2007 22:35:34 GMT
>> Server: Apache/2.0.59 (Win32)
>> X-Powered-By: PHP/4.4.4
>> Cache-Control: public
>> Last-Modified: Tue, 06 Mar 2007 22:35:34 GMT
>> Keep-Alive: timeout=15, max=10000
>> Connection: Keep-Alive
>> Transfer-Encoding: chunked
>> Content-Type: text/html
>>
>>
>> Erica Zhang wrote:
>>
>> > Well, even I use the blinding-cache. It still could not work. Thanks,
>> >
>> > Erica
>> >
>> > David Wortham wrote:
>> >
>> >> Erica,
>> >> I'm not sure why mod_cache should not be able to work (assuming
>> your
>> >> module and pages are configured correctly).
>> >>
>> >> IIRC, JavaScript is used on the presentation request (with the
>> >> webpage),
>> >> whereas the XMLHttpRequest response is a PHP-generated XML document.
>> >> Perhaps your extension ('.php" maybe?) or the mime/content-type
>> >> ("text/xml")
>> >> is what is causing mod_cache to skip the file?
>> >>
>> >> Also, from what I can gather, using mod_cache with mod_proxy (as a
>> >> caching proxy) can alter the effects of mod_cache slightly. You may
>> >> want to
>> >> read up on that.
>> >>
>> >> Try using the following directive with mod_cache:
>> >> CacheIgnoreNoLastMod On
>> >>
>> >> see:
>> >>
>> http://webauth.stanford.edu/manual/mod/mod_cache.html#CacheIgnoreNoLastMod
>>
>> >>
>> >>
>> >> This apparently forces blind-caching which Joe suggests is bad (I
>> >> don't know
>> >> anything about it). Short of that, you just need to read the
>> mod_cache
>> >> manual and make sure your XML response contains the necessary headers
>> >> to get
>> >> mod_cache to work correctly.
>> >>
>> >> Regards,
>> >> Dave
>> >>
>> >>
>> >>
>> >> On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>> >>
>> >>>
>> >>> No, still not work. Infact, mod_cache could work, because it could
>> >>> cache
>> >>> the javascript. But it could not work for dynamic HTTP responses
>> >>> responding to XMLHttpRequests in Ajax technology. So I suspect
>> >>> mod_cache
>> >>> could not support this function. And I need provide such function by
>> >>> myself. I prefer to do it in Apache, a comparatively general way
>> >>> instead
>> >>> of application itself.
>> >>>
>> >>>
>> >>> Erica
>> >>>
>> >>> Joachim Zobel wrote:
>> >>>
>> >>> >Am Montag, den 05.03.2007, 22:53 -0800 schrieb Erica Zhang:
>> >>> >
>> >>> >
>> >>> >>header("Cache-Control: public"); // HTTP/1.1
>> >>> >>header("Expires: " .gmdate ("D, d M Y H:i:s", time() + 60 * 10). "
>> >>> GMT");
>> >>> >>header( "Last-Modified: " .gmdate( 'D, d M Y H:i:s' ). " GMT" );
>> >>> >>echo $response;
>> >>> >>
>> >>> >>
>> >>> >
>> >>> >I am not shure about mod_caches behaviour, but omitting
>> >>> last-modified is
>> >>> >worth a try.
>> >>> >
>> >>> >Sincerely,
>> >>> >Joachim
>> >>> >
>> >>> >
>> >>> >
>> >>>
>> >>>
>> >>
>>
>>
>
Re: Questions on modules to provide cache functions for Apache
Posted by David Wortham <dj...@gmail.com>.
Erica,
My observations of your headers:
(1) The "Last-Modified" line contains the current timestamp (as expected)
(2) Your original question showed that you inserted an "Expires:" header,
but it doesn't show in your response. Did you change your PHP script code
since you asked the original question this morning?
(3) Are you returning XML or HTML? My experience with XMLHttpResponse(s)
required changing the content-type to "text/xml" (not really the issue at
hand)
When you said that you got mod_cache to cache a JavaScript file, was it in
the same directory (and covered by the same mod_cache directives)?
Did you try using the
CacheIgnoreCacheControl On
directive? Did it force the file to cache?
Regards,
Dave
On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>
> I use live http headers to catch the headers. I listed them below. Well
> I found that php file has not been given the http headers. So is this
> the problem for not caching the response produced by it ? Then how can I
> handle this problem ? Also, is there some mod_cache log that I could
> refer ? Thanks.
>
> http://128.189.246.64/gethint.php?q=Eric&sid=0.11837499670287688
>
> GET /gethint.php?q=Eric&sid=0.11837499670287688 HTTP/1.1
> Host: 128.189.246.64
> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2)
> Gecko/20070219 Firefox/2.0.0.2
> Accept:
> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9
> ,text/plain;q=0.8,image/png,*/*;q=0.5
> Accept-Language: en-us,en;q=0.5
> Accept-Encoding: gzip,deflate
> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> Keep-Alive: 300
> Connection: keep-alive
> Referer: http://128.189.246.64/
>
> HTTP/1.x 200 OK
> Date: Tue, 06 Mar 2007 22:35:34 GMT
> Server: Apache/2.0.59 (Win32)
> X-Powered-By: PHP/4.4.4
> Cache-Control: public
> Last-Modified: Tue, 06 Mar 2007 22:35:34 GMT
> Keep-Alive: timeout=15, max=10000
> Connection: Keep-Alive
> Transfer-Encoding: chunked
> Content-Type: text/html
>
>
> Erica Zhang wrote:
>
> > Well, even I use the blinding-cache. It still could not work. Thanks,
> >
> > Erica
> >
> > David Wortham wrote:
> >
> >> Erica,
> >> I'm not sure why mod_cache should not be able to work (assuming your
> >> module and pages are configured correctly).
> >>
> >> IIRC, JavaScript is used on the presentation request (with the
> >> webpage),
> >> whereas the XMLHttpRequest response is a PHP-generated XML document.
> >> Perhaps your extension ('.php" maybe?) or the mime/content-type
> >> ("text/xml")
> >> is what is causing mod_cache to skip the file?
> >>
> >> Also, from what I can gather, using mod_cache with mod_proxy (as a
> >> caching proxy) can alter the effects of mod_cache slightly. You may
> >> want to
> >> read up on that.
> >>
> >> Try using the following directive with mod_cache:
> >> CacheIgnoreNoLastMod On
> >>
> >> see:
> >>
> http://webauth.stanford.edu/manual/mod/mod_cache.html#CacheIgnoreNoLastMod
> >>
> >>
> >> This apparently forces blind-caching which Joe suggests is bad (I
> >> don't know
> >> anything about it). Short of that, you just need to read the mod_cache
> >> manual and make sure your XML response contains the necessary headers
> >> to get
> >> mod_cache to work correctly.
> >>
> >> Regards,
> >> Dave
> >>
> >>
> >>
> >> On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
> >>
> >>>
> >>> No, still not work. Infact, mod_cache could work, because it could
> >>> cache
> >>> the javascript. But it could not work for dynamic HTTP responses
> >>> responding to XMLHttpRequests in Ajax technology. So I suspect
> >>> mod_cache
> >>> could not support this function. And I need provide such function by
> >>> myself. I prefer to do it in Apache, a comparatively general way
> >>> instead
> >>> of application itself.
> >>>
> >>>
> >>> Erica
> >>>
> >>> Joachim Zobel wrote:
> >>>
> >>> >Am Montag, den 05.03.2007, 22:53 -0800 schrieb Erica Zhang:
> >>> >
> >>> >
> >>> >>header("Cache-Control: public"); // HTTP/1.1
> >>> >>header("Expires: " .gmdate ("D, d M Y H:i:s", time() + 60 * 10). "
> >>> GMT");
> >>> >>header( "Last-Modified: " .gmdate( 'D, d M Y H:i:s' ). " GMT" );
> >>> >>echo $response;
> >>> >>
> >>> >>
> >>> >
> >>> >I am not shure about mod_caches behaviour, but omitting
> >>> last-modified is
> >>> >worth a try.
> >>> >
> >>> >Sincerely,
> >>> >Joachim
> >>> >
> >>> >
> >>> >
> >>>
> >>>
> >>
>
>
Re: Questions on modules to provide cache functions for Apache
Posted by Erica Zhang <er...@cs.ubc.ca>.
I use live http headers to catch the headers. I listed them below. Well
I found that php file has not been given the http headers. So is this
the problem for not caching the response produced by it ? Then how can I
handle this problem ? Also, is there some mod_cache log that I could
refer ? Thanks.
http://128.189.246.64/gethint.php?q=Eric&sid=0.11837499670287688
GET /gethint.php?q=Eric&sid=0.11837499670287688 HTTP/1.1
Host: 128.189.246.64
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2)
Gecko/20070219 Firefox/2.0.0.2
Accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://128.189.246.64/
HTTP/1.x 200 OK
Date: Tue, 06 Mar 2007 22:35:34 GMT
Server: Apache/2.0.59 (Win32)
X-Powered-By: PHP/4.4.4
Cache-Control: public
Last-Modified: Tue, 06 Mar 2007 22:35:34 GMT
Keep-Alive: timeout=15, max=10000
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html
Erica Zhang wrote:
> Well, even I use the blinding-cache. It still could not work. Thanks,
>
> Erica
>
> David Wortham wrote:
>
>> Erica,
>> I'm not sure why mod_cache should not be able to work (assuming your
>> module and pages are configured correctly).
>>
>> IIRC, JavaScript is used on the presentation request (with the
>> webpage),
>> whereas the XMLHttpRequest response is a PHP-generated XML document.
>> Perhaps your extension ('.php" maybe?) or the mime/content-type
>> ("text/xml")
>> is what is causing mod_cache to skip the file?
>>
>> Also, from what I can gather, using mod_cache with mod_proxy (as a
>> caching proxy) can alter the effects of mod_cache slightly. You may
>> want to
>> read up on that.
>>
>> Try using the following directive with mod_cache:
>> CacheIgnoreNoLastMod On
>>
>> see:
>> http://webauth.stanford.edu/manual/mod/mod_cache.html#CacheIgnoreNoLastMod
>>
>>
>> This apparently forces blind-caching which Joe suggests is bad (I
>> don't know
>> anything about it). Short of that, you just need to read the mod_cache
>> manual and make sure your XML response contains the necessary headers
>> to get
>> mod_cache to work correctly.
>>
>> Regards,
>> Dave
>>
>>
>>
>> On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>>
>>>
>>> No, still not work. Infact, mod_cache could work, because it could
>>> cache
>>> the javascript. But it could not work for dynamic HTTP responses
>>> responding to XMLHttpRequests in Ajax technology. So I suspect
>>> mod_cache
>>> could not support this function. And I need provide such function by
>>> myself. I prefer to do it in Apache, a comparatively general way
>>> instead
>>> of application itself.
>>>
>>>
>>> Erica
>>>
>>> Joachim Zobel wrote:
>>>
>>> >Am Montag, den 05.03.2007, 22:53 -0800 schrieb Erica Zhang:
>>> >
>>> >
>>> >>header("Cache-Control: public"); // HTTP/1.1
>>> >>header("Expires: " .gmdate ("D, d M Y H:i:s", time() + 60 * 10). "
>>> GMT");
>>> >>header( "Last-Modified: " .gmdate( 'D, d M Y H:i:s' ). " GMT" );
>>> >>echo $response;
>>> >>
>>> >>
>>> >
>>> >I am not shure about mod_caches behaviour, but omitting
>>> last-modified is
>>> >worth a try.
>>> >
>>> >Sincerely,
>>> >Joachim
>>> >
>>> >
>>> >
>>>
>>>
>>
Re: Questions on modules to provide cache functions for Apache
Posted by Issac Goldstand <ma...@beamartyr.net>.
Correct. You'll start seeing subdirectories under you cacheroot
immediately. You can also try turning up the log level to LogLevel
debug and looking at the error_log for more hints.
Issac
Erica Zhang wrote:
> For mod_cache, I just use mod_disk_cache instead of mod_mem_cache. Then
> if the responses are cached, there would be header files and data files
> stored in the responding directory. Right? So I use this way to check if
> the responses are cached.
Re: Questions on modules to provide cache functions for Apache
Posted by Erica Zhang <er...@cs.ubc.ca>.
David,
I printed out the response header, by use of
xmlHttp.getAllResponseHeaders(), which could get the whole headers of
the response. So through it, I could know that the headers have been
added successfully to the responses.
For mod_cache, I just use mod_disk_cache instead of mod_mem_cache. Then
if the responses are cached, there would be header files and data files
stored in the responding directory. Right? So I use this way to check if
the responses are cached.
Erica
David Wortham wrote:
> Erica,
>
> I would follow Joachim's recommendation to:
> You may want to use Firefox with the LiveHttpHeaders Plugin to look at
> the headers, that are actually exchanged (or are you already doing
> that).
>
> My coworker informs me that PHP automatically updates the "last updated"
> header line (to the current time). IIRC, you need to set the headers
> first
> thing in your PHP script otherwise PHP will set headers first. If PHP
> sends
> the header line first, you may be sending two conflicting lines (and
> mod_cache will likely only read/process one of them). If anything is
> echoed
> before a header statement, you will probably not see that particular
> header
> line in the output. LiveHTTPHeaders will allow you to verify the
> "Last-Updated" header line (and any other necessary header lines).
>
> Also, how do you know that the response XML is not being served by
> mod_cache? Are you looking at logfiles, header data, or something else?
> This is important in us being able to help you resolve this issue.
>
> One sure-fire way to know if it is a configuration/directory issue is
> to set
> the following directive:
> CacheIgnoreCacheControl On
>
> This directive should absolutely force every file in that
> Directory/File/Location tag in your httpd.conf to force caching (no
> matter
> what the headers read). If you can't get that to work, I would look into
> your mod_cache config. Also, don't forget to restart your httpd process
> after any changes to httpd (probably not necessary for changes to
> .htaccess
> files).
>
> Regards,
> Dave
>
>
>
> On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>
>>
>> Well, even I use the blinding-cache. It still could not work. Thanks,
>
>
Re: Questions on modules to provide cache functions for Apache
Posted by Erica Zhang <er...@cs.ubc.ca>.
David,
Well, I set CacheIgnoreCacheControl On not in a directory but just <if
modules>, it still could not work. When I want to set it to be the
directory of htdocs, httpd.conf could not pass the parser.
Regards,
Erica
David Wortham wrote:
> Erica,
>
> I would follow Joachim's recommendation to:
> You may want to use Firefox with the LiveHttpHeaders Plugin to look at
> the headers, that are actually exchanged (or are you already doing
> that).
>
> My coworker informs me that PHP automatically updates the "last updated"
> header line (to the current time). IIRC, you need to set the headers
> first
> thing in your PHP script otherwise PHP will set headers first. If PHP
> sends
> the header line first, you may be sending two conflicting lines (and
> mod_cache will likely only read/process one of them). If anything is
> echoed
> before a header statement, you will probably not see that particular
> header
> line in the output. LiveHTTPHeaders will allow you to verify the
> "Last-Updated" header line (and any other necessary header lines).
>
> Also, how do you know that the response XML is not being served by
> mod_cache? Are you looking at logfiles, header data, or something else?
> This is important in us being able to help you resolve this issue.
>
> One sure-fire way to know if it is a configuration/directory issue is
> to set
> the following directive:
> CacheIgnoreCacheControl On
>
> This directive should absolutely force every file in that
> Directory/File/Location tag in your httpd.conf to force caching (no
> matter
> what the headers read). If you can't get that to work, I would look into
> your mod_cache config. Also, don't forget to restart your httpd process
> after any changes to httpd (probably not necessary for changes to
> .htaccess
> files).
>
> Regards,
> Dave
>
>
>
> On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>
>>
>> Well, even I use the blinding-cache. It still could not work. Thanks,
>
>
Re: Questions on modules to provide cache functions for Apache
Posted by David Wortham <dj...@gmail.com>.
Erica,
I would follow Joachim's recommendation to:
You may want to use Firefox with the LiveHttpHeaders Plugin to look at
the headers, that are actually exchanged (or are you already doing
that).
My coworker informs me that PHP automatically updates the "last updated"
header line (to the current time). IIRC, you need to set the headers first
thing in your PHP script otherwise PHP will set headers first. If PHP sends
the header line first, you may be sending two conflicting lines (and
mod_cache will likely only read/process one of them). If anything is echoed
before a header statement, you will probably not see that particular header
line in the output. LiveHTTPHeaders will allow you to verify the
"Last-Updated" header line (and any other necessary header lines).
Also, how do you know that the response XML is not being served by
mod_cache? Are you looking at logfiles, header data, or something else?
This is important in us being able to help you resolve this issue.
One sure-fire way to know if it is a configuration/directory issue is to set
the following directive:
CacheIgnoreCacheControl On
This directive should absolutely force every file in that
Directory/File/Location tag in your httpd.conf to force caching (no matter
what the headers read). If you can't get that to work, I would look into
your mod_cache config. Also, don't forget to restart your httpd process
after any changes to httpd (probably not necessary for changes to .htaccess
files).
Regards,
Dave
On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>
> Well, even I use the blinding-cache. It still could not work. Thanks,
Re: Questions on modules to provide cache functions for Apache
Posted by Erica Zhang <er...@cs.ubc.ca>.
Well, even I use the blinding-cache. It still could not work. Thanks,
Erica
David Wortham wrote:
> Erica,
> I'm not sure why mod_cache should not be able to work (assuming your
> module and pages are configured correctly).
>
> IIRC, JavaScript is used on the presentation request (with the
> webpage),
> whereas the XMLHttpRequest response is a PHP-generated XML document.
> Perhaps your extension ('.php" maybe?) or the mime/content-type
> ("text/xml")
> is what is causing mod_cache to skip the file?
>
> Also, from what I can gather, using mod_cache with mod_proxy (as a
> caching proxy) can alter the effects of mod_cache slightly. You may
> want to
> read up on that.
>
> Try using the following directive with mod_cache:
> CacheIgnoreNoLastMod On
>
> see:
> http://webauth.stanford.edu/manual/mod/mod_cache.html#CacheIgnoreNoLastMod
>
>
> This apparently forces blind-caching which Joe suggests is bad (I
> don't know
> anything about it). Short of that, you just need to read the mod_cache
> manual and make sure your XML response contains the necessary headers
> to get
> mod_cache to work correctly.
>
> Regards,
> Dave
>
>
>
> On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>
>>
>> No, still not work. Infact, mod_cache could work, because it could cache
>> the javascript. But it could not work for dynamic HTTP responses
>> responding to XMLHttpRequests in Ajax technology. So I suspect mod_cache
>> could not support this function. And I need provide such function by
>> myself. I prefer to do it in Apache, a comparatively general way instead
>> of application itself.
>>
>>
>> Erica
>>
>> Joachim Zobel wrote:
>>
>> >Am Montag, den 05.03.2007, 22:53 -0800 schrieb Erica Zhang:
>> >
>> >
>> >>header("Cache-Control: public"); // HTTP/1.1
>> >>header("Expires: " .gmdate ("D, d M Y H:i:s", time() + 60 * 10). "
>> GMT");
>> >>header( "Last-Modified: " .gmdate( 'D, d M Y H:i:s' ). " GMT" );
>> >>echo $response;
>> >>
>> >>
>> >
>> >I am not shure about mod_caches behaviour, but omitting
>> last-modified is
>> >worth a try.
>> >
>> >Sincerely,
>> >Joachim
>> >
>> >
>> >
>>
>>
>
Re: Questions on modules to provide cache functions for Apache
Posted by David Wortham <dj...@gmail.com>.
Erica,
I'm not sure why mod_cache should not be able to work (assuming your
module and pages are configured correctly).
IIRC, JavaScript is used on the presentation request (with the webpage),
whereas the XMLHttpRequest response is a PHP-generated XML document.
Perhaps your extension ('.php" maybe?) or the mime/content-type ("text/xml")
is what is causing mod_cache to skip the file?
Also, from what I can gather, using mod_cache with mod_proxy (as a
caching proxy) can alter the effects of mod_cache slightly. You may want to
read up on that.
Try using the following directive with mod_cache:
CacheIgnoreNoLastMod On
see:
http://webauth.stanford.edu/manual/mod/mod_cache.html#CacheIgnoreNoLastMod
This apparently forces blind-caching which Joe suggests is bad (I don't know
anything about it). Short of that, you just need to read the mod_cache
manual and make sure your XML response contains the necessary headers to get
mod_cache to work correctly.
Regards,
Dave
On 3/6/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>
> No, still not work. Infact, mod_cache could work, because it could cache
> the javascript. But it could not work for dynamic HTTP responses
> responding to XMLHttpRequests in Ajax technology. So I suspect mod_cache
> could not support this function. And I need provide such function by
> myself. I prefer to do it in Apache, a comparatively general way instead
> of application itself.
>
>
> Erica
>
> Joachim Zobel wrote:
>
> >Am Montag, den 05.03.2007, 22:53 -0800 schrieb Erica Zhang:
> >
> >
> >>header("Cache-Control: public"); // HTTP/1.1
> >>header("Expires: " .gmdate ("D, d M Y H:i:s", time() + 60 * 10). "
> GMT");
> >>header( "Last-Modified: " .gmdate( 'D, d M Y H:i:s' ). " GMT" );
> >>echo $response;
> >>
> >>
> >
> >I am not shure about mod_caches behaviour, but omitting last-modified is
> >worth a try.
> >
> >Sincerely,
> >Joachim
> >
> >
> >
>
>
Re: Questions on modules to provide cache functions for Apache
Posted by Erica Zhang <er...@cs.ubc.ca>.
No, still not work. Infact, mod_cache could work, because it could cache
the javascript. But it could not work for dynamic HTTP responses
responding to XMLHttpRequests in Ajax technology. So I suspect mod_cache
could not support this function. And I need provide such function by
myself. I prefer to do it in Apache, a comparatively general way instead
of application itself.
Erica
Joachim Zobel wrote:
>Am Montag, den 05.03.2007, 22:53 -0800 schrieb Erica Zhang:
>
>
>>header("Cache-Control: public"); // HTTP/1.1
>>header("Expires: " .gmdate ("D, d M Y H:i:s", time() + 60 * 10). " GMT");
>>header( "Last-Modified: " .gmdate( 'D, d M Y H:i:s' ). " GMT" );
>>echo $response;
>>
>>
>
>I am not shure about mod_caches behaviour, but omitting last-modified is
>worth a try.
>
>Sincerely,
>Joachim
>
>
>
Re: Questions on modules to provide cache functions for Apache
Posted by Joachim Zobel <jz...@heute-morgen.de>.
Am Montag, den 05.03.2007, 22:53 -0800 schrieb Erica Zhang:
> header("Cache-Control: public"); // HTTP/1.1
> header("Expires: " .gmdate ("D, d M Y H:i:s", time() + 60 * 10). " GMT");
> header( "Last-Modified: " .gmdate( 'D, d M Y H:i:s' ). " GMT" );
> echo $response;
I am not shure about mod_caches behaviour, but omitting last-modified is
worth a try.
Sincerely,
Joachim
Re: Questions on modules to provide cache functions for Apache
Posted by Erica Zhang <er...@cs.ubc.ca>.
Well, my question is not on the usage of mod_cache. In fact, I have used
local applications to add caching headers and configure mod_cache to
catch those HTTP responses. However I could not catch those HTTP
responses. So I wonder if mod_cache could catch dynamic responses which
are responding for those XMLHttpRequest in Ajax technology. If no, I
want to provide a general module to solve the problem.
I have send this kind of questions to user alias but none reply this.
For blind cache, I do not want to use.
Regards,
Erica
Joe Lewis wrote:
> Erica Zhang wrote:
>
>> David,
>>
>> Thanks a lot for your reply. While, I just want to cache HTTP
>> responses produced by PHP scripts. Of course, those responses perhaps
>> include PHP scripts. On the other hand, I know I could do it by use
>> of PHP itself. I just want to provide a general one. This means no
>> matter what kind of script or languages used for server development,
>> for example, ASP, PHP, Java and etc, I could use only one module to
>> cache those HTTP responses. I thought Apache could handle or filter
>> HTTP responses or requests. So I want to add modules to handle
>> caching dynamic HTTP responses problems.
>>
>> However, based on your suggestion, it seems that I have to developed
>> separate ones for Java, ASP, PHP. Right ?
>
>
> If your server is acting as a proxy to another server and it's content
> generation, no - which ever platform you want to develop your caching
> on will cache. If the local server is generating the response, then
> the local application is responsible for either caching or using
> appropriate caching headers. If the caching mechanism is understood,
> just use the existing "mod_cache" and it's associated extensions (e.g.
> mod_mem_cache and mod_disk_cache). Questions regarding those modules
> would be better answered on the users' lists rather than here.
>
>> But is there some general way to cache responses ?
>
>
> Consider modifying whatever is generating the response to include the
> caching headers - a system has been in place for cache control for
> years. If the headers exist, the browsers should only check the
> modification times and request the new page if the modification time
> has changed.
>
> If your server is acting as a proxy to another content, you only have
> two options -
>
> a) modify the content generation server to include the caching headers
>
> b) Force your server to do caching regardless of the headers. This
> will have the wonderful effect in which the web browsers won't have
> control over getting updated docs - and thereby causing network guru's
> to run around like squirrels on caffeine until they realize that a
> server in between is responding with data that should be dynamic but
> isn't because it's been cached. This is because there will be no
> mechanism to determine when the file coming from the generator has
> been updated. It's a blind cache, and I would never suggest a blind
> cache for the sanity of people using the system.
>
> Joe
Re: Questions on modules to provide cache functions for Apache
Posted by Joe Lewis <jo...@joe-lewis.com>.
Erica Zhang wrote:
> David,
>
> Thanks a lot for your reply. While, I just want to cache HTTP
> responses produced by PHP scripts. Of course, those responses perhaps
> include PHP scripts. On the other hand, I know I could do it by use
> of PHP itself. I just want to provide a general one. This means no
> matter what kind of script or languages used for server development,
> for example, ASP, PHP, Java and etc, I could use only one module to
> cache those HTTP responses. I thought Apache could handle or filter
> HTTP responses or requests. So I want to add modules to handle caching
> dynamic HTTP responses problems.
>
> However, based on your suggestion, it seems that I have to developed
> separate ones for Java, ASP, PHP. Right ?
If your server is acting as a proxy to another server and it's content
generation, no - which ever platform you want to develop your caching on
will cache. If the local server is generating the response, then the
local application is responsible for either caching or using appropriate
caching headers. If the caching mechanism is understood, just use the
existing "mod_cache" and it's associated extensions (e.g. mod_mem_cache
and mod_disk_cache). Questions regarding those modules would be better
answered on the users' lists rather than here.
> But is there some general way to cache responses ?
Consider modifying whatever is generating the response to include the
caching headers - a system has been in place for cache control for
years. If the headers exist, the browsers should only check the
modification times and request the new page if the modification time has
changed.
If your server is acting as a proxy to another content, you only have
two options -
a) modify the content generation server to include the caching headers
b) Force your server to do caching regardless of the headers. This
will have the wonderful effect in which the web browsers won't have
control over getting updated docs - and thereby causing network guru's
to run around like squirrels on caffeine until they realize that a
server in between is responding with data that should be dynamic but
isn't because it's been cached. This is because there will be no
mechanism to determine when the file coming from the generator has been
updated. It's a blind cache, and I would never suggest a blind cache
for the sanity of people using the system.
Joe
--
Joseph Lewis <http://sharktooth.org/>
"Divide the fire, and you will sooner put it out." - Publius Syrus
Re: Questions on modules to provide cache functions for Apache
Posted by Issac Goldstand <ma...@beamartyr.net>.
AFAIK, there's no reason that mod_cache shouldn't be able to cache your
output, as long as the request is a GET and not POST, and not otherwise
uncachable (eg, not authenticated, cache headers are present, expires in
future, etc). It runs as an output filter, so the fact that the
response is generated dynamically shouldn't pose a problem. What
happened when you tried using the below config? Does c:/cacheroot
exist? Is it writable by the user Apache runs as?
Issac
Erica Zhang wrote:
> David,
>
> Thanks a lot for your reply. While, I just want to cache HTTP responses
> produced by PHP scripts. Of course, those responses perhaps include PHP
> scripts. On the other hand, I know I could do it by use of PHP itself.
> I just want to provide a general one. This means no matter what kind of
> script or languages used for server development, for example, ASP, PHP,
> Java and etc, I could use only one module to cache those HTTP responses.
> I thought Apache could handle or filter HTTP responses or requests. So I
> want to add modules to handle caching dynamic HTTP responses problems.
>
> However, based on your suggestion, it seems that I have to developed
> separate ones for Java, ASP, PHP. Right ? But is there some general way
> to cache responses ?
>
> Thanks,
>
> Erica
>
> David Wortham wrote:
>
>> Erica,
>> IMO, your caching should take place on the PHP side of things, not
>> Apache
>> or any Apache modules (save for maybe mod_php).
>>
>> Depending on how frequently the cache should refresh, I would either
>> have
>> (1) PHP write the newest response to a file and check the timestamp of
>> the
>> file to check if the cachefile should be updated,
>> (2) Don't use PHP called from a webserver, but rather use PHP called
>> from a
>> cron job, or
>> (3) find out how to use PHP to cache itself (I'm pretty sure Apache won't
>> cache PHP, ASP, etc.)
>>
>> For help on any three of these things, I would recommend asking at a
>> PHP-specific forum/mailing list or on www.php.net (the comments on
>> that site
>> are sometimes extremely helpful).
>>
>> Regards,
>> David Wortham
>>
>>
>>
>>
>> On 3/5/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>>
>>>
>>> Hi,
>>>
>>> I want to develop a filter module to cache responses for XMLHttp
>>> requests for Apache. Before that, I have tried to configure using
>>> mod_cache. I found that it could not be used to cache responses for
>>> XMLHttp requests. However, I am not sure about this, because I am new to
>>> web applications. So before beginning to develop a new module to do this
>>> function, I want to make sure that. Is there some expert tell me about
>>> your idea on this topic or experiences ?
>>>
>>> I tried to give more details below:
>>>
>>> For mod_cache, I use httpd.conf to configure it:
>>>
>>> MaxKeepAliveRequests 10000
>>> <IfModule mpm_winnt.c>
>>> ThreadsPerChild 1900
>>> MaxRequestsPerChild 10000
>>> </IfModule>
>>>
>>> LoadModule cache_module modules/mod_cache.so
>>>
>>> <IfModule mod_cache.c>
>>> CacheForceCompletion 100
>>> CacheDefaultEXPire 3600
>>> CacheMaxExpire 86400
>>> CacheLastModifiedFactor 0.1
>>> LoadModule disk_cache_module modules/mod_disk_cache.so
>>>
>>> <IfModule mod_disk_cache.c>
>>> CacheEnable disk /
>>> CacheRoot c:/cacheroot
>>> CacheSize 327680
>>> CacheDirLength 4
>>> CacheDirLevels 5
>>> CacheGcInterval 4
>>> </IfModule>
>>>
>>> #LoadModule mem_cache_module modules/mod_mem_cache.so
>>> <IfModule mod_mem_cache.c>
>>> CacheEnable mem /
>>> MCacheSize 8192
>>> MCacheMaxObjectCount 10000
>>> MCacheMinObjectSize 1
>>> MCacheMaxObjectSize 51200
>>> </IfModule>
>>> </IfModule>
>>>
>>> On client, I use ajax technology and XMLHttpRequest and on server, I
>>> use php script.
>>> ...
>>> header("Cache-Control: public"); // HTTP/1.1
>>> header("Expires: " .gmdate ("D, d M Y H:i:s", time() + 60 * 10). "
>>> GMT");
>>> header( "Last-Modified: " .gmdate( 'D, d M Y H:i:s' ). " GMT" );
>>> echo $response;
>>> ....
>>> I think apache cache should catch my response produced by PHP. Until
>>> now, I do not think there is something wrong in my code or
>>> configuration. So I conclude that mod_cache could not catch the
>>> responses for XMLHttp requests.
>>>
>>> Regards,
>>>
>>> Erica
>>>
>>>
>>>
>>
Re: Questions on modules to provide cache functions for Apache
Posted by Erica Zhang <er...@cs.ubc.ca>.
David,
Thanks a lot for your reply. While, I just want to cache HTTP responses
produced by PHP scripts. Of course, those responses perhaps include PHP
scripts. On the other hand, I know I could do it by use of PHP itself.
I just want to provide a general one. This means no matter what kind of
script or languages used for server development, for example, ASP, PHP,
Java and etc, I could use only one module to cache those HTTP responses.
I thought Apache could handle or filter HTTP responses or requests. So I
want to add modules to handle caching dynamic HTTP responses problems.
However, based on your suggestion, it seems that I have to developed
separate ones for Java, ASP, PHP. Right ? But is there some general way
to cache responses ?
Thanks,
Erica
David Wortham wrote:
> Erica,
> IMO, your caching should take place on the PHP side of things, not
> Apache
> or any Apache modules (save for maybe mod_php).
>
> Depending on how frequently the cache should refresh, I would either
> have
> (1) PHP write the newest response to a file and check the timestamp of
> the
> file to check if the cachefile should be updated,
> (2) Don't use PHP called from a webserver, but rather use PHP called
> from a
> cron job, or
> (3) find out how to use PHP to cache itself (I'm pretty sure Apache won't
> cache PHP, ASP, etc.)
>
> For help on any three of these things, I would recommend asking at a
> PHP-specific forum/mailing list or on www.php.net (the comments on
> that site
> are sometimes extremely helpful).
>
> Regards,
> David Wortham
>
>
>
>
> On 3/5/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>
>>
>> Hi,
>>
>> I want to develop a filter module to cache responses for XMLHttp
>> requests for Apache. Before that, I have tried to configure using
>> mod_cache. I found that it could not be used to cache responses for
>> XMLHttp requests. However, I am not sure about this, because I am new to
>> web applications. So before beginning to develop a new module to do this
>> function, I want to make sure that. Is there some expert tell me about
>> your idea on this topic or experiences ?
>>
>> I tried to give more details below:
>>
>> For mod_cache, I use httpd.conf to configure it:
>>
>> MaxKeepAliveRequests 10000
>> <IfModule mpm_winnt.c>
>> ThreadsPerChild 1900
>> MaxRequestsPerChild 10000
>> </IfModule>
>>
>> LoadModule cache_module modules/mod_cache.so
>>
>> <IfModule mod_cache.c>
>> CacheForceCompletion 100
>> CacheDefaultEXPire 3600
>> CacheMaxExpire 86400
>> CacheLastModifiedFactor 0.1
>> LoadModule disk_cache_module modules/mod_disk_cache.so
>>
>> <IfModule mod_disk_cache.c>
>> CacheEnable disk /
>> CacheRoot c:/cacheroot
>> CacheSize 327680
>> CacheDirLength 4
>> CacheDirLevels 5
>> CacheGcInterval 4
>> </IfModule>
>>
>> #LoadModule mem_cache_module modules/mod_mem_cache.so
>> <IfModule mod_mem_cache.c>
>> CacheEnable mem /
>> MCacheSize 8192
>> MCacheMaxObjectCount 10000
>> MCacheMinObjectSize 1
>> MCacheMaxObjectSize 51200
>> </IfModule>
>> </IfModule>
>>
>> On client, I use ajax technology and XMLHttpRequest and on server, I
>> use php script.
>> ...
>> header("Cache-Control: public"); // HTTP/1.1
>> header("Expires: " .gmdate ("D, d M Y H:i:s", time() + 60 * 10). "
>> GMT");
>> header( "Last-Modified: " .gmdate( 'D, d M Y H:i:s' ). " GMT" );
>> echo $response;
>> ....
>> I think apache cache should catch my response produced by PHP. Until
>> now, I do not think there is something wrong in my code or
>> configuration. So I conclude that mod_cache could not catch the
>> responses for XMLHttp requests.
>>
>> Regards,
>>
>> Erica
>>
>>
>>
>
Re: Questions on modules to provide cache functions for Apache
Posted by David Wortham <dj...@gmail.com>.
Erica,
IMO, your caching should take place on the PHP side of things, not Apache
or any Apache modules (save for maybe mod_php).
Depending on how frequently the cache should refresh, I would either have
(1) PHP write the newest response to a file and check the timestamp of the
file to check if the cachefile should be updated,
(2) Don't use PHP called from a webserver, but rather use PHP called from a
cron job, or
(3) find out how to use PHP to cache itself (I'm pretty sure Apache won't
cache PHP, ASP, etc.)
For help on any three of these things, I would recommend asking at a
PHP-specific forum/mailing list or on www.php.net (the comments on that site
are sometimes extremely helpful).
Regards,
David Wortham
On 3/5/07, Erica Zhang <er...@cs.ubc.ca> wrote:
>
> Hi,
>
> I want to develop a filter module to cache responses for XMLHttp
> requests for Apache. Before that, I have tried to configure using
> mod_cache. I found that it could not be used to cache responses for
> XMLHttp requests. However, I am not sure about this, because I am new to
> web applications. So before beginning to develop a new module to do this
> function, I want to make sure that. Is there some expert tell me about
> your idea on this topic or experiences ?
>
> I tried to give more details below:
>
> For mod_cache, I use httpd.conf to configure it:
>
> MaxKeepAliveRequests 10000
> <IfModule mpm_winnt.c>
> ThreadsPerChild 1900
> MaxRequestsPerChild 10000
> </IfModule>
>
> LoadModule cache_module modules/mod_cache.so
>
> <IfModule mod_cache.c>
> CacheForceCompletion 100
> CacheDefaultEXPire 3600
> CacheMaxExpire 86400
> CacheLastModifiedFactor 0.1
> LoadModule disk_cache_module modules/mod_disk_cache.so
>
> <IfModule mod_disk_cache.c>
> CacheEnable disk /
> CacheRoot c:/cacheroot
> CacheSize 327680
> CacheDirLength 4
> CacheDirLevels 5
> CacheGcInterval 4
> </IfModule>
>
> #LoadModule mem_cache_module modules/mod_mem_cache.so
> <IfModule mod_mem_cache.c>
> CacheEnable mem /
> MCacheSize 8192
> MCacheMaxObjectCount 10000
> MCacheMinObjectSize 1
> MCacheMaxObjectSize 51200
> </IfModule>
> </IfModule>
>
> On client, I use ajax technology and XMLHttpRequest and on server, I
> use php script.
> ...
> header("Cache-Control: public"); // HTTP/1.1
> header("Expires: " .gmdate ("D, d M Y H:i:s", time() + 60 * 10). " GMT");
> header( "Last-Modified: " .gmdate( 'D, d M Y H:i:s' ). " GMT" );
> echo $response;
> ....
> I think apache cache should catch my response produced by PHP. Until
> now, I do not think there is something wrong in my code or
> configuration. So I conclude that mod_cache could not catch the
> responses for XMLHttp requests.
>
> Regards,
>
> Erica
>
>
>