35 static $statusMessage = [
37 101 =>
'Switching Protocols',
42 203 =>
'Non-Authoritative Information',
44 205 =>
'Reset Content',
45 206 =>
'Partial Content',
46 207 =>
'Multi-Status',
47 300 =>
'Multiple Choices',
48 301 =>
'Moved Permanently',
51 304 =>
'Not Modified',
53 307 =>
'Temporary Redirect',
55 401 =>
'Unauthorized',
56 402 =>
'Payment Required',
59 405 =>
'Method Not Allowed',
60 406 =>
'Not Acceptable',
61 407 =>
'Proxy Authentication Required',
62 408 =>
'Request Timeout',
65 411 =>
'Length Required',
66 412 =>
'Precondition Failed',
67 413 =>
'Request Entity Too Large',
68 414 =>
'Request-URI Too Large',
69 415 =>
'Unsupported Media Type',
70 416 =>
'Request Range Not Satisfiable',
71 417 =>
'Expectation Failed',
72 422 =>
'Unprocessable Entity',
74 424 =>
'Failed Dependency',
75 428 =>
'Precondition Required',
76 429 =>
'Too Many Requests',
77 431 =>
'Request Header Fields Too Large',
78 500 =>
'Internal Server Error',
79 501 =>
'Not Implemented',
81 503 =>
'Service Unavailable',
82 504 =>
'Gateway Timeout',
83 505 =>
'HTTP Version Not Supported',
84 507 =>
'Insufficient Storage',
85 511 =>
'Network Authentication Required',
87 return isset( $statusMessage[
$code] ) ? $statusMessage[
$code] : null;
97 static $version = null;
98 $message = self::getMessage(
$code );
99 if ( $message === null ) {
100 trigger_error(
"Unknown HTTP status code $code", E_USER_WARNING );
104 if ( $version === null ) {
105 $version = isset( $_SERVER[
'SERVER_PROTOCOL'] ) &&
106 $_SERVER[
'SERVER_PROTOCOL'] ===
'HTTP/1.0' ?
111 header(
"HTTP/$version $code $message" );
static header($code)
Output an HTTP status code header.
static getMessage($code)
Get the message associated with an HTTP response status code.
this hook is for auditing only or null if authentication failed before getting that far or null if we can t even determine that probably a stub it is not rendered in wiki pages or galleries in category pages allow injecting custom HTML after the section Any uses of the hook need to handle escaping see BaseTemplate::getToolbox and BaseTemplate::makeListItem for details on the format of individual items inside of this array or by returning and letting standard HTTP rendering take place modifiable or by returning false and taking over the output modifiable & $code
injection txt This is an overview of how MediaWiki makes use of dependency injection The design described here grew from the discussion of RFC T384 The term dependency this means that anything an object needs to operate should be injected from the the object itself should only know narrow no concrete implementation of the logic it relies on The requirement to inject everything typically results in an architecture that based on two main types of and essentially stateless service objects that use other service objects to operate on the value objects As of the beginning MediaWiki is only starting to use the DI approach Much of the code still relies on global state or direct resulting in a highly cyclical dependency which acts as the top level factory for services in MediaWiki which can be used to gain access to default instances of various services MediaWikiServices however also allows new services to be defined and default services to be redefined Services are defined or redefined by providing a callback the instantiator that will return a new instance of the service When it will create an instance of MediaWikiServices and populate it with the services defined in the files listed by thereby bootstrapping the DI framework Per $wgServiceWiringFiles lists includes ServiceWiring php
1.8.8