[HTTPHeaderSettings] config

Next topic

Author	Message
Diego Barcia	Sunday 21 October 2007 12:06:08 pm Regarding the Expires header, ¿how can the home page be identified? See http://ez.no/developer/articles/ez_publish_performance_optimization_part_3_of_3_practical_cache_and_template_solutions/cacheable_headers "Cacheable Headers" of "Practical Cache and Template Solutions" I give a real world example but simple. There's a website that has three levels: the home page, sections that list articles, and the articles. I want everything to expire in the future except listings (level 2) and specially the home page (level 1), which is the page that changes more often. So I want that articles (level 3) return 172801 as an Expires. And listings (level 2), and specially the front page (level 1), return -7200. 172801 means 48 hours plus 1 second, which is (I read somewhere) the minimum value that YSlow, the Firebug optimization plugin, takes as a "good far future" Expires header. Say the sections are /a/ and /b/. With this configuration, I've succeded in making eZ Publish to put negative Expires on section listings /a/ and /b/, and a positive Expires on the third level (the articles), and was yet amazed by ez Publish, once again! But the home page is still expiring in 48 hours from now, as the articles: [HTTPHeaderSettings] CustomHeader=enabled Expires[] Expires[/]=172801 Expires[/a]=-7200;0 Expires[/b]=-7200;0 I tried identifying the home page with a Expires[/content/view/full/2]=-7200, but it doesn't work. If anyone knows if this could be done.

Author

Message

Sunday 21 October 2007 12:06:08 pm

Regarding the Expires header, ¿how can the home page be identified?

See http://ez.no/developer/articles/ez_publish_performance_optimization_part_3_of_3_practical_cache_and_template_solutions/cacheable_headers
"Cacheable Headers" of "Practical Cache and Template Solutions"

I give a real world example but simple. There's a website that has three levels: the home page, sections that list articles, and the articles.

I want everything to expire in the future except listings (level 2) and specially the home page (level 1), which is the page that changes more often.

So I want that articles (level 3) return 172801 as an Expires. And listings (level 2), and specially the front page (level 1), return -7200.

172801 means 48 hours plus 1 second, which is (I read somewhere) the minimum value that YSlow, the Firebug optimization plugin, takes as a "good far future" Expires header.

Say the sections are /a/ and /b/. With this configuration, I've succeded in making eZ Publish to put negative Expires on section listings /a/ and /b/, and a positive Expires on the third level (the articles), and was yet amazed by ez Publish, once again! But the home page is still expiring in 48 hours from now, as the articles:

[HTTPHeaderSettings]
CustomHeader=enabled
Expires[]
Expires[/]=172801
Expires[/a]=-7200;0
Expires[/b]=-7200;0

I tried identifying the home page with a Expires[/content/view/full/2]=-7200, but it doesn't work. If anyone knows if this could be done.

eZ debug

Timing:	Jan 19 2025 07:06:49
Script start
Timing:	Jan 19 2025 07:06:49
Module start 'layout'
Timing:	Jan 19 2025 07:06:49
Module start 'content'
Timing:	Jan 19 2025 07:06:50
Module end 'content'
Timing:	Jan 19 2025 07:06:50
Script end

Main resources:

Total runtime	1.4108 sec
Peak memory usage	4,096.0000 KB
Database Queries	46

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0086	589.1563	152.6250
Module start 'layout'	0.0086	0.0038	741.7813	39.4453
Module start 'content'	0.0124	1.3969	781.2266	407.5234
Module end 'content'	1.4093	0.0015	1,188.7500	8.1641
Script end	1.4108		1,196.9141

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0038	0.2662	16	0.0002
Check MTime	0.0014	0.0975	16	0.0001
Mysql Total
Database connection	0.0014	0.0958	1	0.0014
Mysqli_queries	1.3648	96.7386	46	0.0297
Looping result	0.0006	0.0406	44	0.0000
Template Total	1.3500	95.7	2	0.6750
Template load	0.0026	0.1871	2	0.0013
Template processing	1.3474	95.5015	2	0.6737
Template load and register function	0.0002	0.0152	1	0.0002
states
state_id_array	0.0029	0.2057	1	0.0029
state_identifier_array	0.0039	0.2743	2	0.0019
Override
Cache load	0.0022	0.1556	18	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0433	1	0.0006
Fetch class attribute name	0.0014	0.0985	1	0.0014
XML
Image XML parsing	0.0001	0.0077	1	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0006	1	0.0000
General
dbfile	0.0033	0.2340	10	0.0003
String conversion	0.0000	0.0009	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
1	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 8 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs