Cookies

Next topic

Author	Message
Philip Valentino	Tuesday 10 February 2004 11:27:17 am Hi, I'm using Ezpublish 3.2 and I wanted to find out for certain whether or not it uses persistant cookies. From what I've read on the boards it sounds like it just uses session/temporary cookies or maybe even cookieless sessions? But I need to be sure because of the privacy policy that I must adhere to. Phil
Marco Zinn	Tuesday 10 February 2004 1:15:37 pm Hi, ez3 uses the sessionhandling of PHP. That means, if this is using Cookies, ez will use cookies. If it is using URLs with Session-IDs, ez will use this. ez CAN override it. Example: We have a default 3.2 installation. This is just using session cookies (clients must accept them, but thes are not stored to disc). I think, ez stores the session key in a database for 3 days by default, but i think, this is not related to your privacy policy. When we needed a "stored" cookie (in a file) for doing an offline copy of non-public-pages, we just changed one value in ezPublish's site.ini. But it's easy to find out: Just set your browser to "ask me, when i receive a cookie" and it will give you information. We use Mozilla Firebird/Firefox, which shows all cookie info, when the server sends the cookie. Marco http://www.hyperroad-design.com

Author

Message

Tuesday 10 February 2004 11:27:17 am

Hi,

I'm using Ezpublish 3.2 and I wanted to find out for certain whether or not it uses persistant cookies. From what I've read on the boards it sounds like it just uses session/temporary cookies or maybe even cookieless sessions? But I need to be sure because of the privacy policy that I must adhere to.

Phil

Marco Zinn

Tuesday 10 February 2004 1:15:37 pm

Hi,
ez3 uses the sessionhandling of PHP. That means, if this is using Cookies, ez will use cookies. If it is using URLs with Session-IDs, ez will use this.
ez CAN override it.
Example: We have a default 3.2 installation. This is just using session cookies (clients must accept them, but thes are not stored to disc). I think, ez stores the session key in a database for 3 days by default, but i think, this is not related to your privacy policy.
When we needed a "stored" cookie (in a file) for doing an offline copy of non-public-pages, we just changed one value in ezPublish's site.ini.
But it's easy to find out: Just set your browser to "ask me, when i receive a cookie" and it will give you information. We use Mozilla Firebird/Firefox, which shows all cookie info, when the server sends the cookie.

Marco
http://www.hyperroad-design.com

eZ debug

Timing:	Jan 31 2025 06:11:37
Script start
Timing:	Jan 31 2025 06:11:37
Module start 'layout'
Timing:	Jan 31 2025 06:11:37
Module start 'content'
Timing:	Jan 31 2025 06:11:37
Module end 'content'
Timing:	Jan 31 2025 06:11:37
Script end

Main resources:

Total runtime	0.0160 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0056	587.9766	151.1797
Module start 'layout'	0.0056	0.0032	739.1563	36.5781
Module start 'content'	0.0088	0.0057	775.7344	90.0625
Module end 'content'	0.0146	0.0014	865.7969	29.9922
Script end	0.0159		895.7891

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	16.3452	14	0.0002
Check MTime	0.0011	6.9887	14	0.0001
Mysql Total
Database connection	0.0007	4.5939	1	0.0007
Mysqli_queries	0.0030	19.0552	3	0.0010
Looping result	0.0000	0.1823	1	0.0000
Template Total	0.0010	6.4	1	0.0010
Template load	0.0008	5.0510	1	0.0008
Template processing	0.0002	1.2848	1	0.0002
Override
Cache load	0.0006	3.5586	1	0.0006
General
dbfile	0.0013	8.1898	8	0.0002
String conversion	0.0000	0.0613	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs