|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2006-06-25 13:36 UTC] tony2001@php.net
[2006-06-25 14:16 UTC] php at raj dot homelinux dot com
[2006-06-25 14:36 UTC] tony2001@php.net
[2006-06-25 20:06 UTC] php at raj dot homelinux dot com
[2006-07-20 15:57 UTC] tony2001@php.net
[2006-07-28 01:00 UTC] php-bugs at lists dot php dot net
|
|||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Tue Dec 02 18:00:01 2025 UTC |
Description: ------------ putenv() claims that the env variables are reset to their original values when the script exits. HOwever, this doesn't seem to be happening - as a result, if the env var TZ is set from a php script, it affects apache2 logs, changing the timestamp for all subsequent gets served by the process that ran this php script which set TZ. Reproduce code: --------------- set $timezone different from server timezone and run: putenv("TZ=".$timeZone); -- then do a few more gets and check the apache logs, you will see something like: xx.xx.xx.xx - - [19/Jun/2006:23:05:18 -0400] "GET ..." xx.xx.xx.xx - - [19/Jun/2006:23:05:18 -0400] "GET ..." xx.xx.xx.xx - - [20/Jun/2006:13:05:11 +1000] "GET ..." (see how the timestamp in the apache log flipped from -0400 to +1000.. thats the problem) Expected result: ---------------- Timestamps should remain consistent Actual result: -------------- Timestamps are not consistent (see example above)