Search Results

  1. Phar::mungServer () should only be called within the stub of a phar archive. Defines a list of up to 4 $_SERVER variables that should be modified for execution. Variables that can be modified to remove traces of phar execution are REQUEST_URI, PHP_SELF, SCRIPT_NAME and SCRIPT_FILENAME. On its own, this method does nothing. Only when combined with Phar::webPhar () does it take effect, and only ...

  2. phar:: mungServer () doit être appelée seulement dans le conteneur de chargement d'une archive phar. Définit une liste de maximum 4 variables $_SERVER qui doivent être modifiées lors de l'exécution.

  3. Phar::mungServer () should only be called within the stub of a phar archive. Defines a list of up to 4 $_SERVER variables that should be modified for execution. Variables that can be modified to remove traces of phar execution are REQUEST_URI, PHP_SELF, SCRIPT_NAME and SCRIPT_FILENAME. On its own, this method does nothing.

  4. Phar::mungServer () should only be called within the stub of a phar archive. Defines a list of up to 4 $_SERVER variables that should be modified for execution. Variables that can be modified to remove traces of phar execution are REQUEST_URI, PHP_SELF, SCRIPT_NAME and SCRIPT_FILENAME. On its own, this method does nothing.

  5. Simple usage example of `Phar::mungServer ()`. The PHP function Phar::mungServer is used to modify specific $_SERVER variables for the purpose of execution. It allows for defining a list of up to four $_SERVER variables that should be altered.

  6. Phar::mungServer () should only be called within the stub of a phar archive. Defines a list of up to 4 $_SERVER variables that should be modified for execution. Variables that can be modified to remove traces of phar execution are REQUEST_URI, PHP_SELF, SCRIPT_NAME and SCRIPT_FILENAME. On its own, this method does nothing.

  7. English PHP documentation. Contribute to php/doc-en development by creating an account on GitHub.

  1. People also search for