Req #15133 [Opn->Bgs]: SSI

Edit report at http://bugs.php.net/bug.php?id=15133&edit=1 ID: 15133 Updated by: jani@php.net Reported by: tim dot lokot at s1 dot com dot au Summary: SSI -Status: Open +Status: Bogus Type: Feature/Change Request -Package: Feature/Change Request +Package: *General Issues Operating System: Windows PHP Version: 4.1.1 Block user comment: N Private report: N New Comment: Nope. Previous Comments: ------------------------------------------------------------------------ [2002-01-21 17:31:01] tim dot lokot at s1 dot com dot au 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. ------------------------------------------------------------------------ [2002-01-21 02:04:49] imajes@php.net 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] daniel@php.net 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] tim dot lokot at s1 dot com dot au 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] daniel@php.net 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 ------------------------------------------------------------------------ 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/bug.php?id=15133 -- Edit this bug report at http://bugs.php.net/bug.php?id=15133&edit=1