[PHP-DEV] Bug #15133 Updated: SSI
ID: 15133 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Feature/Change Request Operating System: Windows PHP Version: 4.1.1 New Comment: Ok, I've run some tests on my server and I can setup another filtered extension. I guess this is one way to run it. Seeing as this was a feature request, I thought it might be useful to be able to control this setting programatically. If this isn't going to be added to the list of things to add, then please put this in some kind of configuration documentation somewhere. This question comes up a lot more than obviously you guys are aware of. Previous Comments: [2002-01-21 02:04:49] [EMAIL PROTECTED] alternatively, why not have your isp make a new filtered extension, like .pssi or something, which has the executable set as php.exe -q ? [2002-01-20 23:56:30] [EMAIL PROTECTED] Well, on UN*X, too you don't have to supply the path to PHP. But as you are implying, a script is either called normally OR from a SSI include. So every script which is called by SSI could have a php -q at the beginning, right? Your set_expose would therefore be redundant (unless -q is not possible from within IIS). Is it possible, or not, to run a PHP-script with -q on IIS? Kind Regards, Daniel Lorch [2002-01-20 22:32:19] [EMAIL PROTECTED] Under IIS, you do not have to supply the path to the executable in every script. That's the nature of windows. It works via file extension association. My solution is to create a function called set_expose(off) or whatever fits in with the php naming conventions so that this can be set at runtime from within the script. Thus forcing php to not send out any headers by itself. [2002-01-20 22:28:34] [EMAIL PROTECTED] But this a completely intended behaviour. On UN*X you have to provide the -q as well in _every script_ which should be used as output called from a SSI directive. Where do you have to make this setting? Globally for all PHP scripts? Or can it be done in every script. I don't know IIS, sorry. Kind Regards, Daniel Lorch [2002-01-20 22:11:59] [EMAIL PROTECTED] Under IIS you specify what script engine runs your php file. Basically says that all files with extension .php are run by c:/php/php.exe or whatever the executable is. You COULD put the -q in there, but that would apply for all users. Can you specify -q at runtime so that my ISP (or any ISP for that matter) doesn't have to set explicit settings for this? That way it gets left up to the programmer HOW they want their php scripts run. Forcing -q on all users would mean that everyone of the ISP's clients would have to output all the headers just to get their scripts running. The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/?id=15133 Edit this bug report at http://bugs.php.net/?id=15133edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #15133 Updated: SSI
ID: 15133 Updated by: daniel Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Feature/Change Request Operating System: Windows PHP Version: 4.1.1 New Comment: At least on UN*X systems you can run PHP perfectly as SSI - just do a SSI include !--#include virtual=phpscript.cgi -- where phpscript.cgi is a script which first line points to your PHP executable: #!/usr/bin/php which could also be c:\progra~\php\php.exe (I think). Or did I completely misunderstand you? Also the X-Powered-By can be switched off. Either by /usr/bin/php -q which omits all HTTP-headers (such as Content-type and X-Powered-By) or by configuration directive: expose_php = On ; Decides whether PHP may expose the fact that it is installed ; server (e.g., by adding its signature to the Web server header). ; It is no security threat in any way, but it makes it possible ; to determine whether you use PHP on your server or not. Kind Regards, Daniel Lorch Previous Comments: [2002-01-20 21:43:01] [EMAIL PROTECTED] Is it possible to enable future versions of PHP to be run as an SSI directive so that languages like Perl do not have to be used instead for this purpose? Currently PHP sends out the X-Powered-By headers everytime it's run including all the other default headers making it difficult to run PHP as SSI without having all the headers display to the screen. Edit this bug report at http://bugs.php.net/?id=15133edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #15133 Updated: SSI
ID: 15133 Updated by: rasmus Reported By: [EMAIL PROTECTED] Old Status: Open Status: Bogus Bug Type: Feature/Change Request Operating System: Windows PHP Version: 4.1.1 New Comment: Adding -q is sufficient. No PHP changes needed here. Previous Comments: [2002-01-20 22:00:05] [EMAIL PROTECTED] At least on UN*X systems you can run PHP perfectly as SSI - just do a SSI include !--#include virtual=phpscript.cgi -- where phpscript.cgi is a script which first line points to your PHP executable: #!/usr/bin/php which could also be c:\progra~\php\php.exe (I think). Or did I completely misunderstand you? Also the X-Powered-By can be switched off. Either by /usr/bin/php -q which omits all HTTP-headers (such as Content-type and X-Powered-By) or by configuration directive: expose_php = On ; Decides whether PHP may expose the fact that it is installed ; server (e.g., by adding its signature to the Web server header). ; It is no security threat in any way, but it makes it possible ; to determine whether you use PHP on your server or not. Kind Regards, Daniel Lorch [2002-01-20 21:43:01] [EMAIL PROTECTED] Is it possible to enable future versions of PHP to be run as an SSI directive so that languages like Perl do not have to be used instead for this purpose? Currently PHP sends out the X-Powered-By headers everytime it's run including all the other default headers making it difficult to run PHP as SSI without having all the headers display to the screen. Edit this bug report at http://bugs.php.net/?id=15133edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #15133 Updated: SSI
ID: 15133 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Old Status: Bogus Status: Open Bug Type: Feature/Change Request Operating System: Windows PHP Version: 4.1.1 New Comment: You kind of understood I was aware of the expose setting in the ini file, but it would be nice to be able to modify this at runtime. How can you run that -q command from within a windows environment like IIS? Previous Comments: [2002-01-20 22:02:26] [EMAIL PROTECTED] Adding -q is sufficient. No PHP changes needed here. [2002-01-20 22:00:05] [EMAIL PROTECTED] At least on UN*X systems you can run PHP perfectly as SSI - just do a SSI include !--#include virtual=phpscript.cgi -- where phpscript.cgi is a script which first line points to your PHP executable: #!/usr/bin/php which could also be c:\progra~\php\php.exe (I think). Or did I completely misunderstand you? Also the X-Powered-By can be switched off. Either by /usr/bin/php -q which omits all HTTP-headers (such as Content-type and X-Powered-By) or by configuration directive: expose_php = On ; Decides whether PHP may expose the fact that it is installed ; server (e.g., by adding its signature to the Web server header). ; It is no security threat in any way, but it makes it possible ; to determine whether you use PHP on your server or not. Kind Regards, Daniel Lorch [2002-01-20 21:43:01] [EMAIL PROTECTED] Is it possible to enable future versions of PHP to be run as an SSI directive so that languages like Perl do not have to be used instead for this purpose? Currently PHP sends out the X-Powered-By headers everytime it's run including all the other default headers making it difficult to run PHP as SSI without having all the headers display to the screen. Edit this bug report at http://bugs.php.net/?id=15133edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #15133 Updated: SSI
ID: 15133 Updated by: rasmus Reported By: [EMAIL PROTECTED] Old Status: Open Status: Feedback Bug Type: Feature/Change Request Operating System: Windows PHP Version: 4.1.1 New Comment: php.exe -q doesn't work on Windows? Previous Comments: [2002-01-20 22:04:09] [EMAIL PROTECTED] You kind of understood I was aware of the expose setting in the ini file, but it would be nice to be able to modify this at runtime. How can you run that -q command from within a windows environment like IIS? [2002-01-20 22:02:26] [EMAIL PROTECTED] Adding -q is sufficient. No PHP changes needed here. [2002-01-20 22:00:05] [EMAIL PROTECTED] At least on UN*X systems you can run PHP perfectly as SSI - just do a SSI include !--#include virtual=phpscript.cgi -- where phpscript.cgi is a script which first line points to your PHP executable: #!/usr/bin/php which could also be c:\progra~\php\php.exe (I think). Or did I completely misunderstand you? Also the X-Powered-By can be switched off. Either by /usr/bin/php -q which omits all HTTP-headers (such as Content-type and X-Powered-By) or by configuration directive: expose_php = On ; Decides whether PHP may expose the fact that it is installed ; server (e.g., by adding its signature to the Web server header). ; It is no security threat in any way, but it makes it possible ; to determine whether you use PHP on your server or not. Kind Regards, Daniel Lorch [2002-01-20 21:43:01] [EMAIL PROTECTED] Is it possible to enable future versions of PHP to be run as an SSI directive so that languages like Perl do not have to be used instead for this purpose? Currently PHP sends out the X-Powered-By headers everytime it's run including all the other default headers making it difficult to run PHP as SSI without having all the headers display to the screen. Edit this bug report at http://bugs.php.net/?id=15133edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #15133 Updated: SSI
ID: 15133 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Old Status: Feedback Status: Open Bug Type: Feature/Change Request Operating System: Windows PHP Version: 4.1.1 New Comment: Under IIS you specify what script engine runs your php file. Basically says that all files with extension .php are run by c:/php/php.exe or whatever the executable is. You COULD put the -q in there, but that would apply for all users. Can you specify -q at runtime so that my ISP (or any ISP for that matter) doesn't have to set explicit settings for this? That way it gets left up to the programmer HOW they want their php scripts run. Forcing -q on all users would mean that everyone of the ISP's clients would have to output all the headers just to get their scripts running. Previous Comments: [2002-01-20 22:08:46] [EMAIL PROTECTED] php.exe -q doesn't work on Windows? [2002-01-20 22:04:09] [EMAIL PROTECTED] You kind of understood I was aware of the expose setting in the ini file, but it would be nice to be able to modify this at runtime. How can you run that -q command from within a windows environment like IIS? [2002-01-20 22:02:26] [EMAIL PROTECTED] Adding -q is sufficient. No PHP changes needed here. [2002-01-20 22:00:05] [EMAIL PROTECTED] At least on UN*X systems you can run PHP perfectly as SSI - just do a SSI include !--#include virtual=phpscript.cgi -- where phpscript.cgi is a script which first line points to your PHP executable: #!/usr/bin/php which could also be c:\progra~\php\php.exe (I think). Or did I completely misunderstand you? Also the X-Powered-By can be switched off. Either by /usr/bin/php -q which omits all HTTP-headers (such as Content-type and X-Powered-By) or by configuration directive: expose_php = On ; Decides whether PHP may expose the fact that it is installed ; server (e.g., by adding its signature to the Web server header). ; It is no security threat in any way, but it makes it possible ; to determine whether you use PHP on your server or not. Kind Regards, Daniel Lorch [2002-01-20 21:43:01] [EMAIL PROTECTED] Is it possible to enable future versions of PHP to be run as an SSI directive so that languages like Perl do not have to be used instead for this purpose? Currently PHP sends out the X-Powered-By headers everytime it's run including all the other default headers making it difficult to run PHP as SSI without having all the headers display to the screen. Edit this bug report at http://bugs.php.net/?id=15133edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #15133 Updated: SSI
ID: 15133 Updated by: daniel Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Feature/Change Request Operating System: Windows PHP Version: 4.1.1 New Comment: But this a completely intended behaviour. On UN*X you have to provide the -q as well in _every script_ which should be used as output called from a SSI directive. Where do you have to make this setting? Globally for all PHP scripts? Or can it be done in every script. I don't know IIS, sorry. Kind Regards, Daniel Lorch Previous Comments: [2002-01-20 22:11:59] [EMAIL PROTECTED] Under IIS you specify what script engine runs your php file. Basically says that all files with extension .php are run by c:/php/php.exe or whatever the executable is. You COULD put the -q in there, but that would apply for all users. Can you specify -q at runtime so that my ISP (or any ISP for that matter) doesn't have to set explicit settings for this? That way it gets left up to the programmer HOW they want their php scripts run. Forcing -q on all users would mean that everyone of the ISP's clients would have to output all the headers just to get their scripts running. [2002-01-20 22:08:46] [EMAIL PROTECTED] php.exe -q doesn't work on Windows? [2002-01-20 22:04:09] [EMAIL PROTECTED] You kind of understood I was aware of the expose setting in the ini file, but it would be nice to be able to modify this at runtime. How can you run that -q command from within a windows environment like IIS? [2002-01-20 22:02:26] [EMAIL PROTECTED] Adding -q is sufficient. No PHP changes needed here. [2002-01-20 22:00:05] [EMAIL PROTECTED] At least on UN*X systems you can run PHP perfectly as SSI - just do a SSI include !--#include virtual=phpscript.cgi -- where phpscript.cgi is a script which first line points to your PHP executable: #!/usr/bin/php which could also be c:\progra~\php\php.exe (I think). Or did I completely misunderstand you? Also the X-Powered-By can be switched off. Either by /usr/bin/php -q which omits all HTTP-headers (such as Content-type and X-Powered-By) or by configuration directive: expose_php = On ; Decides whether PHP may expose the fact that it is installed ; server (e.g., by adding its signature to the Web server header). ; It is no security threat in any way, but it makes it possible ; to determine whether you use PHP on your server or not. Kind Regards, Daniel Lorch The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/?id=15133 Edit this bug report at http://bugs.php.net/?id=15133edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #15133 Updated: SSI
ID: 15133 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Feature/Change Request Operating System: Windows PHP Version: 4.1.1 New Comment: Under IIS, you do not have to supply the path to the executable in every script. That's the nature of windows. It works via file extension association. My solution is to create a function called set_expose(off) or whatever fits in with the php naming conventions so that this can be set at runtime from within the script. Thus forcing php to not send out any headers by itself. Previous Comments: [2002-01-20 22:28:34] [EMAIL PROTECTED] But this a completely intended behaviour. On UN*X you have to provide the -q as well in _every script_ which should be used as output called from a SSI directive. Where do you have to make this setting? Globally for all PHP scripts? Or can it be done in every script. I don't know IIS, sorry. Kind Regards, Daniel Lorch [2002-01-20 22:11:59] [EMAIL PROTECTED] Under IIS you specify what script engine runs your php file. Basically says that all files with extension .php are run by c:/php/php.exe or whatever the executable is. You COULD put the -q in there, but that would apply for all users. Can you specify -q at runtime so that my ISP (or any ISP for that matter) doesn't have to set explicit settings for this? That way it gets left up to the programmer HOW they want their php scripts run. Forcing -q on all users would mean that everyone of the ISP's clients would have to output all the headers just to get their scripts running. [2002-01-20 22:08:46] [EMAIL PROTECTED] php.exe -q doesn't work on Windows? [2002-01-20 22:04:09] [EMAIL PROTECTED] You kind of understood I was aware of the expose setting in the ini file, but it would be nice to be able to modify this at runtime. How can you run that -q command from within a windows environment like IIS? [2002-01-20 22:02:26] [EMAIL PROTECTED] Adding -q is sufficient. No PHP changes needed here. The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/?id=15133 Edit this bug report at http://bugs.php.net/?id=15133edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #15133 Updated: SSI
ID: 15133 Updated by: daniel Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Feature/Change Request Operating System: Windows PHP Version: 4.1.1 New Comment: Well, on UN*X, too you don't have to supply the path to PHP. But as you are implying, a script is either called normally OR from a SSI include. So every script which is called by SSI could have a php -q at the beginning, right? Your set_expose would therefore be redundant (unless -q is not possible from within IIS). Is it possible, or not, to run a PHP-script with -q on IIS? Kind Regards, Daniel Lorch Previous Comments: [2002-01-20 22:32:19] [EMAIL PROTECTED] Under IIS, you do not have to supply the path to the executable in every script. That's the nature of windows. It works via file extension association. My solution is to create a function called set_expose(off) or whatever fits in with the php naming conventions so that this can be set at runtime from within the script. Thus forcing php to not send out any headers by itself. [2002-01-20 22:28:34] [EMAIL PROTECTED] But this a completely intended behaviour. On UN*X you have to provide the -q as well in _every script_ which should be used as output called from a SSI directive. Where do you have to make this setting? Globally for all PHP scripts? Or can it be done in every script. I don't know IIS, sorry. Kind Regards, Daniel Lorch [2002-01-20 22:11:59] [EMAIL PROTECTED] Under IIS you specify what script engine runs your php file. Basically says that all files with extension .php are run by c:/php/php.exe or whatever the executable is. You COULD put the -q in there, but that would apply for all users. Can you specify -q at runtime so that my ISP (or any ISP for that matter) doesn't have to set explicit settings for this? That way it gets left up to the programmer HOW they want their php scripts run. Forcing -q on all users would mean that everyone of the ISP's clients would have to output all the headers just to get their scripts running. [2002-01-20 22:08:46] [EMAIL PROTECTED] php.exe -q doesn't work on Windows? [2002-01-20 22:04:09] [EMAIL PROTECTED] You kind of understood I was aware of the expose setting in the ini file, but it would be nice to be able to modify this at runtime. How can you run that -q command from within a windows environment like IIS? The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/?id=15133 Edit this bug report at http://bugs.php.net/?id=15133edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #15133 Updated: SSI
ID: 15133 Updated by: imajes Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Feature/Change Request Operating System: Windows PHP Version: 4.1.1 New Comment: alternatively, why not have your isp make a new filtered extension, like .pssi or something, which has the executable set as php.exe -q ? Previous Comments: [2002-01-20 23:56:30] [EMAIL PROTECTED] Well, on UN*X, too you don't have to supply the path to PHP. But as you are implying, a script is either called normally OR from a SSI include. So every script which is called by SSI could have a php -q at the beginning, right? Your set_expose would therefore be redundant (unless -q is not possible from within IIS). Is it possible, or not, to run a PHP-script with -q on IIS? Kind Regards, Daniel Lorch [2002-01-20 22:32:19] [EMAIL PROTECTED] Under IIS, you do not have to supply the path to the executable in every script. That's the nature of windows. It works via file extension association. My solution is to create a function called set_expose(off) or whatever fits in with the php naming conventions so that this can be set at runtime from within the script. Thus forcing php to not send out any headers by itself. [2002-01-20 22:28:34] [EMAIL PROTECTED] But this a completely intended behaviour. On UN*X you have to provide the -q as well in _every script_ which should be used as output called from a SSI directive. Where do you have to make this setting? Globally for all PHP scripts? Or can it be done in every script. I don't know IIS, sorry. Kind Regards, Daniel Lorch [2002-01-20 22:11:59] [EMAIL PROTECTED] Under IIS you specify what script engine runs your php file. Basically says that all files with extension .php are run by c:/php/php.exe or whatever the executable is. You COULD put the -q in there, but that would apply for all users. Can you specify -q at runtime so that my ISP (or any ISP for that matter) doesn't have to set explicit settings for this? That way it gets left up to the programmer HOW they want their php scripts run. Forcing -q on all users would mean that everyone of the ISP's clients would have to output all the headers just to get their scripts running. [2002-01-20 22:08:46] [EMAIL PROTECTED] php.exe -q doesn't work on Windows? The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/?id=15133 Edit this bug report at http://bugs.php.net/?id=15133edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
