Home  >  Article  >  Backend Development  >  Bug in session.save_path in PHP4.0.0 (reprint)_PHP tutorial

Bug in session.save_path in PHP4.0.0 (reprint)_PHP tutorial

WBOY
WBOYOriginal
2016-07-13 17:07:35808browse

Author: limodou
Here I would like to report to you a bug I found in version 4.0.0, which is limited to the Windows version. That is: under version 4.0.0, if
session.save_path uses an absolute directory, that is, if a drive letter is added, the drive letter will not work. For example, session.save_path is set to
c: emp, and the c: emp directory exists. But when the php program file is on another disk, such as on the f disk, c: does not work. Instead, it looks for the emp directory on the f drive when processing
session. If there is no emp directory on disk f, the following error will be reported:
Warning: open( emp/sess_0beef27320944002381aa93c9ec0968d, O_RDWR) failed: m (2)
in f: esta.php3 on line 2
Warning: open( emp/sess_0beef27320944002381aa93c9ec0968d, O_RDWR) failed: m (2)
in Unknown on line 0
Warning: Failed to write session data. Please check that the current setting of
session.save_path is correct (c : emp) in Unknown on line 0
 If you create a temp directory on the f drive, the error disappears. I checked the source program, and it looked very laborious, but I couldn't find it. I found that what I was looking at
was the source code of version 4.0.1pl2. So I upgraded PHP to version 4.0.1pl2 and ran it again. Hey, the error disappeared. It seems that version 4.0.1pl2 has
corrected this error.
It is recommended that everyone install version 4.0.1pl2.
When setting session.save_path at the same time, the directory separator can be '/' or ''.

www.bkjia.comtruehttp: //www.bkjia.com/PHPjc/630246.htmlTechArticleAuthor: limodou Here I would like to report to you a bug I found in version 4.0.0, which is limited to the windows version. That is: under version 4.0.0, if session.save_path uses an absolute directory, add...
Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn