This status code is primarily intended to be used with the Link header, letting the user agent start preloading resources while the server prepares a response or preconnect to an origin from which the page will need resources.
The request has been received but not yet acted upon. It is noncommittal, since there is no way in HTTP to later send an asynchronous response indicating the outcome of the request. It is intended for cases where another process or server handles the request, or for batch processing.
Status Server
Download 🔥 https://bytlly.com/2y3B1E 🔥
This response code means the returned metadata is not exactly the same as is available from the origin server, but is collected from a local or a third-party copy. This is mostly used for mirrors or backups of another resource. Except for that specific case, the 200 OK response is preferred to this status.
The server sends this response to direct the client to get the requested resource at another URI with the same method that was used in the prior request. This has the same semantics as the 302 Found HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.
The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
This response code is reserved for future use. The initial aim for creating this code was using it for digital payment systems, however this status code is used very rarely and no standard convention exists.
The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server.
The server cannot find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 Forbidden to hide the existence of a resource from an unauthorized client. This response code is probably the most well known due to its frequent occurrence on the web.
This response is sent on an idle connection by some servers, even without any previous request by the client. It means that the server would like to shut down this unused connection. This response is used much more since some browsers, like Chrome, Firefox 27+, or IE9, use HTTP pre-connection mechanisms to speed up surfing. Also note that some servers merely shut down the connection without sending this message.
This response is sent when the requested content has been permanently deleted from server, with no forwarding address. Clients are expected to remove their caches and links to the resource. The HTTP specification intends this status code to be used for "limited-time, promotional services". APIs should not feel compelled to indicate resources that have been deleted with this status code.
The request was directed at a server that is not able to produce a response. This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.
The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. The server sends an Upgrade header in a 426 response to indicate the required protocol(s).
The origin server requires the request to be conditional. This response is intended to prevent the 'lost update' problem, where a client GETs a resource's state, modifies it and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.
The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded. Note that together with this response, a user-friendly page explaining the problem should be sent. This response should be used for temporary conditions and the Retry-After HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also take care about the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached.
The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.
\n The request has been received but not yet acted upon.\n It is noncommittal, since there is no way in HTTP to later send an asynchronous response indicating the outcome of the request.\n It is intended for cases where another process or server handles the request, or for batch processing.\n
\n This response code means the returned metadata is not exactly the same as is available from the origin server, but is collected from a local or a third-party copy.\n This is mostly used for mirrors or backups of another resource.\n Except for that specific case, the 200 OK response is preferred to this status.\n
\n The server sends this response to direct the client to get the requested resource at another URI with the same method that was used in the prior request.\n This has the same semantics as the 302 Found HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.\n
\n This response code is reserved for future use.\n The initial aim for creating this code was using it for digital payment systems, however this status code is used very rarely and no standard convention exists.\n
\n The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource.\n Unlike 401 Unauthorized, the client's identity is known to the server.\n
\n The server cannot find the requested resource.\n In the browser, this means the URL is not recognized.\n In an API, this can also mean that the endpoint is valid but the resource itself does not exist.\n Servers may also send this response instead of 403 Forbidden to hide the existence of a resource from an unauthorized client.\n This response code is probably the most well known due to its frequent occurrence on the web.\n
\n This response is sent on an idle connection by some servers, even without any previous request by the client.\n It means that the server would like to shut down this unused connection.\n This response is used much more since some browsers, like Chrome, Firefox 27+, or IE9, use HTTP pre-connection mechanisms to speed up surfing.\n Also note that some servers merely shut down the connection without sending this message.\n
\n This response is sent when the requested content has been permanently deleted from server, with no forwarding address.\n Clients are expected to remove their caches and links to the resource.\n The HTTP specification intends this status code to be used for \"limited-time, promotional services\".\n APIs should not feel compelled to indicate resources that have been deleted with this status code.\n
\n The request was directed at a server that is not able to produce a response.\n This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.\n
\n The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol.\n The server sends an Upgrade header in a 426 response to indicate the required protocol(s).\n
\n The origin server requires the request to be conditional.\n This response is intended to prevent the 'lost update' problem, where a client GETs a resource's state, modifies it and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.\n
\n The server is not ready to handle the request.\n Common causes are a server that is down for maintenance or that is overloaded.\n Note that together with this response, a user-friendly page explaining the problem should be sent.\n This response should be used for temporary conditions and the Retry-After HTTP header should, if possible, contain the estimated time before the recovery of the service.\n The webmaster must also take care about the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached.\n
Since SNMP support went away in at least in version 2 of the server software (see: SNMP HOWTO), administrators have to gather information about the status and statistics of the server by other means. FreeRADIUS offers a special status server. This (virtual) server can be queried, providing a wide range of information about the actual server state and the packages being processed. So please use it to monitor your installation.
The configuration for the status server is automatically created in the sites-available directory.By default, this server is enabled and can be queried from every client. This behavior is controlled in the security section of the main config file.
FreeRADIUS will only respond to status-server messages, if the status-server virtual server has been enabled. To do this,create a link from the sites-enabled directory to the status file in the sites-available directory: 2351a5e196