leesiulung Posted May 23, 2007 Share Posted May 23, 2007 Is there any reasons any more to even consider Server Side Includes over the include()/require() functionality implemented in PHP? Also, according to the manual: "Files for including are first looked in include_path relative to the current working directory and then in include_path relative to the directory of current script. E.g. if your include_path is ., current working directory is /www/, you included include/a.php and there is include "b.php" in that file, b.php is first looked in /www/ and then in /www/include/. If filename begins with ./ or ../, it is looked only in include_path relative to the current working directory. " The last sentence in quoted paragraph mentions a way to force includes to only be relative. However, what do you do if you are on a windows system... "./c:\phpincludepath" ??? Link to comment https://forums.phpfreaks.com/topic/52705-ssi-vs-includerequire/ Share on other sites More sharing options...
marf Posted May 23, 2007 Share Posted May 23, 2007 is it file:/// ? Link to comment https://forums.phpfreaks.com/topic/52705-ssi-vs-includerequire/#findComment-260239 Share on other sites More sharing options...
leesiulung Posted May 25, 2007 Author Share Posted May 25, 2007 is it file:/// ? I think it is, however, only 2 slashes though. I still wonder if there is any reason to use server side includes (SSI) instead of include() or require(). Any1? Link to comment https://forums.phpfreaks.com/topic/52705-ssi-vs-includerequire/#findComment-261841 Share on other sites More sharing options...
hitman6003 Posted May 26, 2007 Share Posted May 26, 2007 Windows servers still obey relative paths... "./" will always mean "current directory" in every operating system Link to comment https://forums.phpfreaks.com/topic/52705-ssi-vs-includerequire/#findComment-261897 Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.