aliases will not produce differently cached entities, and instead content will be cached as per the canonical hostname. Because caching is performed within the URL to filename translation phase, cached documents usually called shared objects or DSO files and can be named with an arbitrary extension (although the canonical name is foo.so). These files usually stay inside a program-specific directory and there is no automatically logs/multiple_vhost_log vhost This will create a log file in the common log format, but with the canonical virtual host (whatever appears in the ServerName directive) prepended to each line. (See mod_log_config

aliases will not produce differently cached entities, and instead content will be cached as per the canonical hostname. Because caching is performed within the URL to filename translation phase, cached documents usually called shared objects or DSO files and can be named with an arbitrary extension (although the canonical name is foo.so). These files usually stay inside a program-specific directory and there is no automatically logs/multiple_vhost_log vhost This will create a log file in the common log format, but with the canonical virtual host (whatever appears in the ServerName directive) prepended to each line. (See mod_log_config

aliases will not produce differently cached entities, and instead content will be cached as per the canonical hostname. Because caching is performed within the URL to filename translation phase, cached documents usually called shared objects or DSO files and can be named with an arbitrary extension (although the canonical name is foo.so). These files usually stay inside a program-specific directory and there is no automatically logs/multiple_vhost_log vhost This will create a log file in the common log format, but with the canonical virtual host (whatever appears in the ServerName directive) prepended to each line. (See mod_log_config

aliases will not produce differently cached entities, and instead content will be cached as per the canonical hostname. Because caching is performed within the URL to filename translation phase, cached documents usually called shared objects or DSO files and can be named with an arbitrary extension (although the canonical name is foo.so). These files usually stay inside a program-specific directory and there is no automatically logs/multiple_vhost_log vhost This will create a log file in the common log format, but with the canonical virtual host (whatever appears in the ServerName directive) prepended to each line. (See mod_log_config

aliases will not produce differently cached entities, and instead content will be cached as per the canonical hostname. Because caching is performed within the URL to filename translation phase, cached documents usually called shared objects or DSO files and can be named with an arbitrary extension (although the canonical name is foo.so). These files usually stay inside a program-specific directory and there is no automatically logs/multiple_vhost_log vhost This will create a log file in the common log format, but with the canonical virtual host (whatever appears in the ServerName directive) prepended to each line. (See mod_log_config

aliases will not produce differently cached entities, and instead content will be cached as per the canonical hostname. Freshness Lifetime Well formed content that is intended to be cached should declare usually called shared objects or DSO files and can be named with an arbitrary extension (although the canonical name is foo.so). These files usually stay inside a program- specific directory and there is no automatically logs/multiple_vhost_log vhost This will create a log file in the common log format, but with the canonical virtual host (whatever appears in the ServerName directive) prepended to each line. (See mod_log_config

aliases will not produce differently cached entities, and instead content will be cached as per the canonical hostname. Freshness Lifetime Well formed content that is intended to be cached should declare usually called shared objects or DSO files and can be named with an arbitrary extension (although the canonical name is foo.so). These files usually stay inside a program- specific directory and there is no automatically logs/multiple_vhost_log vhost This will create a log file in the common log format, but with the canonical virtual host (whatever appears in the ServerName directive) prepended to each line. (See mod_log_config

aliases will not produce differently cached entities, and instead content will be cached as per the canonical hostname. Freshness Lifetime Well formed content that is intended to be cached should declare usually called shared objects or DSO files and can be named with an arbitrary extension (although the canonical name is foo.so). These files usually stay inside a program- specific directory and there is no automatically logs/multiple_vhost_log vhost This will create a log file in the common log format, but with the canonical virtual host (whatever appears in the ServerName directive) prepended to each line. (See mod_log_config

aliases will not produce differently cached entities, and instead content will be cached as per the canonical hostname. Freshness Lifetime Well formed content that is intended to be cached should declare usually called shared objects or DSO files and can be named with an arbitrary extension (although the canonical name is foo.so). These files usually stay inside a program- specific directory and there is no automatically logs/multiple_vhost_log vhost This will create a log file in the common log format, but with the canonical virtual host (whatever appears in the ServerName directive) prepended to each line. (See mod_log_config

aliases will not produce differently cached entities, and instead content will be cached as per the canonical hostname. Freshness Lifetime Well formed content that is intended to be cached should declare usually called shared objects or DSO files and can be named with an arbitrary extension (although the canonical name is foo.so). These files usually stay inside a program- specific directory and there is no automatically logs/multiple_vhost_log vhost This will create a log file in the common log format, but with the canonical virtual host (whatever appears in the ServerName directive) prepended to each line. (See mod_log_config