![]()
|
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7">
定義済ã®å¤‰æ•°ã‚µãƒ¼ãƒå¤‰æ•°: $_SERVER
$_SERVER ã¯ã€ãƒ˜ãƒƒãƒ€ã€ãƒ‘スã€ã‚¹ã‚¯ãƒªãƒ—トã®ä½ç½®ã® よã†ãªæƒ…å ±ã‚’æœ‰ã™ã‚‹é…列ã§ã™ã€‚ã“ã®é…列ã®ã‚¨ãƒ³ãƒˆãƒªã¯ã€Webサーãƒã«ã‚ˆã‚Š ç”Ÿæˆã•れã¾ã™ã€‚å…¨ã¦ã®WebサーãƒãŒã“れら全ã¦ã‚’æä¾›ã™ã‚‹ä¿éšœã¯ã‚りã¾ã› ん。サーãƒã¯ã€ã“れらã®ã„ãã¤ã‹ã‚’çœç•¥ã—ãŸã‚Šã€ã“ã®ä¸€è¦§ã«ãªã„ä»–ã®ã‚‚ ã®ã‚’定義ã™ã‚‹å¯èƒ½æ€§ãŒã‚りã¾ã™ã€‚ã“れらã®å¤‰æ•°ã®å¤šãã¯ã€ CGI 1.1 specificationã§å®šç¾©ã• れã¦ã„ã¾ã™ã€‚ã—ãŸãŒã£ã¦ã€ã“れらã«ã¤ã„ã¦ã¯å®šç¾©ã•れã¦ã„ã‚‹ã“ã¨ã‚’期待 ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ ã“れã¯ã€'スーパーグãƒãƒ¼ãƒãƒ«(superglobal)'ã€ã¾ãŸã¯è‡ªå‹•ã‚°ãƒãƒ¼ãƒãƒ« (automatic global)ã€å¤‰æ•°ã§ã™ã€‚ã“れã¯ã€ã‚¹ã‚¯ãƒªãƒ—トã®å…¨ã¦ã®ã‚¹ã‚³ãƒ¼ãƒ— ã§åˆ©ç”¨å¯èƒ½ã§ã‚ã‚‹ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚関数やメソッドã®ä¸ã‹ã‚‰ã“ã®å¤‰æ•° ã«ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹éš›ã« $HTTP_SERVER_VARS ã®ã‚ˆã†ã« global $_SERVER; ã¨ã™ã‚‹å¿…è¦ã¯ã‚りã¾ã›ã‚“。 $HTTP_SERVER_VARS ã®æœ€åˆã®æƒ…å ±ã¯åŒã˜ã§ã™ãŒã€ autoglobalã§ã¯ã‚りã¾ã›ã‚“。(HTTP_SERVER_VARS 㨠$_SERVERã¯ç•°ãªã‚‹å¤‰æ•°ã§ã‚りã€PHPã¯ç•°ãªã‚‹å¤‰æ•°ã¨ ã—ã¦å‡¦ç†ã‚’行ã†ã“ã¨ã«æ³¨æ„ã—ã¦ä¸‹ã•ã„) register_globals ディ レクティブをè¨å®šã—ãŸå ´åˆã€ã“れらã®å¤‰æ•°ã¯ã€ã‚¹ã‚¯ãƒªãƒ—トã®ã‚°ãƒãƒ¼ãƒãƒ« スコープã€ã¤ã¾ã‚Šã€é…列 $_SERVER åŠã³ $HTTP_SERVER_VARS 以外ã®ã‚°ãƒãƒ¼ãƒãƒ«å¤‰æ•°ã¨ã—㦠利用å¯èƒ½ã¨ãªã‚Šã¾ã™ã€‚é–¢é€£æƒ…å ±ã«ã¤ã„ã¦ã¯ã€ register_globalsã®ä½¿ç”¨æ³• ã¨ã„ã†åå‰ã®ã‚»ã‚ュリティã«é–¢ã™ã‚‹ç« ã‚’å‚照下ã•ã„。 ã“れらã®å„ã‚°ãƒãƒ¼ãƒãƒ«å¤‰æ•°ã¯ã€autoglobalã§ã¯ã‚りã¾ã›ã‚“。 以下ã®å„è¦ç´ ã®ã„ãã¤ã‹ã¯ $_SERVER ã«ç¾ã‚Œãªã„å¯èƒ½æ€§ãŒã‚りã¾ã™ã€‚PHP をコマンドラインã§å®Ÿè¡Œã—ã¦ã„ã‚‹å ´åˆã«ã¯ã€ä½¿ç”¨ã§ãã‚‹ã‚‚ã®ã¯åƒ…ã‹ã§ã‚ã‚‹ ã“ã¨ã«æ³¨æ„ã—ã¦ä¸‹ã•ã„。
環境変数: $_ENV
These variables are imported into PHP's global namespace from the environment under which the PHP parser is running. Many are provided by the shell under which PHP is running and different systems are likely running different kinds of shells, a definitive list is impossible. Please see your shell's documentation for a list of defined environment variables. Other environment variables include the CGI variables, placed there regardless of whether PHP is running as a server module or CGI processor. This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $_ENV; to access it within functions or methods, as you do with $HTTP_ENV_VARS. $HTTP_ENV_VARS contains the same initial information, but is not an autoglobal. (Note that HTTP_ENV_VARS and $_ENV are different variables and that PHP handles them as such) If the register_globals directive is set, then these variables will also be made available in the global scope of the script; i.e., separate from the $_ENV and $HTTP_ENV_VARS arrays. For related information, see the security chapter titled Using Register Globals. These individual globals are not autoglobals. HTTPクッã‚ー: $_COOKIE
An associative array of variables passed to the current script via HTTP cookies. Automatically global in any scope. This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $_COOKIE; to access it within functions or methods, as you do with $HTTP_COOKIE_VARS. $HTTP_COOKIE_VARS contains the same initial information, but is not an autoglobal. (Note that HTTP_COOKIE_VARS and $_COOKIE are different variables and that PHP handles them as such) If the register_globals directive is set, then these variables will also be made available in the global scope of the script; i.e., separate from the $_COOKIE and $HTTP_COOKIE_VARS arrays. For related information, see the security chapter titled Using Register Globals. These individual globals are not autoglobals. HTTP GET 変数: $_GET
An associative array of variables passed to the current script via the HTTP GET method. Automatically global in any scope. This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $_GET; to access it within functions or methods, as you do with $HTTP_GET_VARS. $HTTP_GET_VARS contains the same initial information, but is not an autoglobal. (Note that HTTP_GET_VARS and $_GET are different variables and that PHP handles them as such) If the register_globals directive is set, then these variables will also be made available in the global scope of the script; i.e., separate from the $_GET and $HTTP_GET_VARS arrays. For related information, see the security chapter titled Using Register Globals. These individual globals are not autoglobals. HTTP POST 変数: $_POST
An associative array of variables passed to the current script via the HTTP POST method. Automatically global in any scope. This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $_POST; to access it within functions or methods, as you do with $HTTP_POST_VARS. $HTTP_POST_VARS contains the same initial information, but is not an autoglobal. (Note that HTTP_POST_VARS and $_POST are different variables and that PHP handles them as such) If the register_globals directive is set, then these variables will also be made available in the global scope of the script; i.e., separate from the $_POST and $HTTP_POST_VARS arrays. For related information, see the security chapter titled Using Register Globals. These individual globals are not autoglobals. HTTPファイルアップãƒãƒ¼ãƒ‰å¤‰æ•°: $_FILES
An associative array of items uploaded to the current script via the HTTP POST method. Automatically global in any scope. This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $_FILES; to access it within functions or methods, as you do with $HTTP_POST_FILES. $HTTP_POST_FILES contains the same information, but is not an autoglobal. If the register_globals directive is set, then these variables will also be made available in the global scope of the script; i.e., separate from the $_FILES and $HTTP_POST_FILES arrays. For related information, see the security chapter titled Using Register Globals. These individual globals are not autoglobals. リクエスト変数: $_REQUEST
An associative array consisting of the contents of $_GET, $_POST, $_COOKIE, and $_FILES. This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $_REQUEST; to access it within functions or methods. If the register_globals directive is set, then these variables will also be made available in the global scope of the script; i.e., separate from the $_REQUEST array. For related information, see the security chapter titled Using Register Globals. These individual globals are not autoglobals. セッション変数: $_SESSION
An associative array containing session variables available to the current script. See the Session functions documentation for more information on how this is used. This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $_SESSION; to access it within functions or methods, as you do with $HTTP_SESSION_VARS. $HTTP_SESSION_VARS contains the same information, but is not an autoglobal. If the register_globals directive is set, then these variables will also be made available in the global scope of the script; i.e., separate from the $_SESSION and $HTTP_SESSION_VARS arrays. For related information, see the security chapter titled Using Register Globals. These individual globals are not autoglobals. ã‚°ãƒãƒ¼ãƒãƒ«å¤‰æ•°: $GLOBALS
An associative array containing references to all variables which are currently defined in the global scope of the script. The variable names are the keys of the array. This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $GLOBALS; to access it within functions or methods. The previous error message: $php_errormsg$php_errormsg is a variable containing the text of the last error message generated by PHP. This variable will only be available within the scope in which the error occurred, and only if the track_errors configuration option is turned on (it defaults to off).
|