From 71a426bfc86de00956b1bb4ecbb02a376b64e7f4 Mon Sep 17 00:00:00 2001
From: Costanzo-Francesco
+ The local loopback mechanism may be used to run a network service on a
+ host without requiring a physical network interface, or without making the
+ service accessible from the networks the computer may be connected to. For
+ example, a locally installed website may be accessed from a Web browser by
+ the URL http://localhost to display its home page. The name localhost
+ normally resolves to the IPv4 loopback address 127.0.0.1, and to the IPv6
+ loopback address ::1.
+
+ IPv4 network standards reserve the entire address block 127.0.0.0/8 (more
+ than 16 million addresses) for loopback purposes.[2] That means any packet
+ sent to any of those addresses is looped back. The address 127.0.0.1 is
+ the standard address for IPv4 loopback traffic; the rest are not supported
+ by all operating systems. However, they can be used to set up multiple
+ server applications on the host, all listening on the same port number.
+ The IPv6 standard assigns only a single address for loopback: ::1. The
+ resolution of the name localhost to one or more IP addresses is normally
+ configured by the following lines in the operating system's hosts
+ file:IPv4 network standards reserve the entire address block 127.0.0.0/8
+ (more than 16 million addresses) for loopback purposes.[2] That means any
+ packet sent to any of those addresses is looped back. The address
+ 127.0.0.1 is the standard address for IPv4 loopback traffic; the rest are
+ not supported by all operating systems. However, they can be used to set
+ up multiple server applications on the host, all listening on the same
+ port number. The IPv6 standard assigns only a single address for loopback:
+ ::1. The resolution of the name localhost to one or more IP addresses is
+ normally configured by the following lines in the operating system's hosts
+ file:
+ The name localhost is reserved for loopback purposes by RFC 6761
+ (Special-Use Domain Names),[4] which achieved the Proposed Standard
+ maturity level in February 2013. The standard sets forth a number of
+ special considerations governing the use of the name in the Domain Name
+ System:
+ The processing of any packet sent to a loopback address, is implemented in
+ the link layer of the TCP/IP stack. Such packets are never passed to any
+ network interface controller (NIC) or hardware device driver and must not
+ appear outside of a computing system, or be routed by any router. This
+ permits software testing and local services in the absence of any hardware
+ network interfaces.
+ The releases of the MySQL database differentiate between the use of the
+ hostname localhost and the use of the addresses 127.0.0.1 and ::1.[7] When
+ using localhost as the destination in a client connector interface of an
+ application, the MySQL application programming interface connects to the
+ database using a Unix domain socket, while a TCP connection via the
+ loopback interface requires the direct use of the explicit address.
+
+ The local loopback mechanism may be used to run a network service on a
+ host without requiring a physical network interface, or without making the
+ service accessible from the networks the computer may be connected to. For
+ example, a locally installed website may be accessed from a Web browser by
+ the URL http://localhost to display its home page. The name localhost
+ normally resolves to the IPv4 loopback address 127.0.0.1, and to the IPv6
+ loopback address ::1.
+
+ IPv4 network standards reserve the entire address block 127.0.0.0/8 (more
+ than 16 million addresses) for loopback purposes.[2] That means any packet
+ sent to any of those addresses is looped back. The address 127.0.0.1 is
+ the standard address for IPv4 loopback traffic; the rest are not supported
+ by all operating systems. However, they can be used to set up multiple
+ server applications on the host, all listening on the same port number.
+ The IPv6 standard assigns only a single address for loopback: ::1. The
+ resolution of the name localhost to one or more IP addresses is normally
+ configured by the following lines in the operating system's hosts
+ file:IPv4 network standards reserve the entire address block 127.0.0.0/8
+ (more than 16 million addresses) for loopback purposes.[2] That means any
+ packet sent to any of those addresses is looped back. The address
+ 127.0.0.1 is the standard address for IPv4 loopback traffic; the rest are
+ not supported by all operating systems. However, they can be used to set
+ up multiple server applications on the host, all listening on the same
+ port number. The IPv6 standard assigns only a single address for loopback:
+ ::1. The resolution of the name localhost to one or more IP addresses is
+ normally configured by the following lines in the operating system's hosts
+ file:
+ The name localhost is reserved for loopback purposes by RFC 6761
+ (Special-Use Domain Names),[4] which achieved the Proposed Standard
+ maturity level in February 2013. The standard sets forth a number of
+ special considerations governing the use of the name in the Domain Name
+ System:
+ The processing of any packet sent to a loopback address, is implemented in
+ the link layer of the TCP/IP stack. Such packets are never passed to any
+ network interface controller (NIC) or hardware device driver and must not
+ appear outside of a computing system, or be routed by any router. This
+ permits software testing and local services in the absence of any hardware
+ network interfaces.
+ The releases of the MySQL database differentiate between the use of the
+ hostname localhost and the use of the addresses 127.0.0.1 and ::1.[7] When
+ using localhost as the destination in a client connector interface of an
+ application, the MySQL application programming interface connects to the
+ database using a Unix domain socket, while a TCP connection via the
+ loopback interface requires the direct use of the explicit address.
+
+ The local loopback mechanism may be used to run a network service on a
+ host without requiring a physical network interface, or without making the
+ service accessible from the networks the computer may be connected to. For
+ example, a locally installed website may be accessed from a Web browser by
+ the URL http://localhost to display its home page. The name localhost
+ normally resolves to the IPv4 loopback address 127.0.0.1, and to the IPv6
+ loopback address ::1.
+
+ IPv4 network standards reserve the entire address block 127.0.0.0/8 (more
+ than 16 million addresses) for loopback purposes.[2] That means any packet
+ sent to any of those addresses is looped back. The address 127.0.0.1 is
+ the standard address for IPv4 loopback traffic; the rest are not supported
+ by all operating systems. However, they can be used to set up multiple
+ server applications on the host, all listening on the same port number.
+ The IPv6 standard assigns only a single address for loopback: ::1. The
+ resolution of the name localhost to one or more IP addresses is normally
+ configured by the following lines in the operating system's hosts
+ file:IPv4 network standards reserve the entire address block 127.0.0.0/8
+ (more than 16 million addresses) for loopback purposes.[2] That means any
+ packet sent to any of those addresses is looped back. The address
+ 127.0.0.1 is the standard address for IPv4 loopback traffic; the rest are
+ not supported by all operating systems. However, they can be used to set
+ up multiple server applications on the host, all listening on the same
+ port number. The IPv6 standard assigns only a single address for loopback:
+ ::1. The resolution of the name localhost to one or more IP addresses is
+ normally configured by the following lines in the operating system's hosts
+ file:
+ The name localhost is reserved for loopback purposes by RFC 6761
+ (Special-Use Domain Names),[4] which achieved the Proposed Standard
+ maturity level in February 2013. The standard sets forth a number of
+ special considerations governing the use of the name in the Domain Name
+ System:
+ The processing of any packet sent to a loopback address, is implemented in
+ the link layer of the TCP/IP stack. Such packets are never passed to any
+ network interface controller (NIC) or hardware device driver and must not
+ appear outside of a computing system, or be routed by any router. This
+ permits software testing and local services in the absence of any hardware
+ network interfaces.
+ The releases of the MySQL database differentiate between the use of the
+ hostname localhost and the use of the addresses 127.0.0.1 and ::1.[7] When
+ using localhost as the destination in a client connector interface of an
+ application, the MySQL application programming interface connects to the
+ database using a Unix domain socket, while a TCP connection via the
+ loopback interface requires the direct use of the explicit address.
+
+ The local loopback mechanism may be used to run a network service on a
+ host without requiring a physical network interface, or without making the
+ service accessible from the networks the computer may be connected to. For
+ example, a locally installed website may be accessed from a Web browser by
+ the URL http://localhost to display its home page. The name localhost
+ normally resolves to the IPv4 loopback address 127.0.0.1, and to the IPv6
+ loopback address ::1.
+
+ IPv4 network standards reserve the entire address block 127.0.0.0/8 (more
+ than 16 million addresses) for loopback purposes.[2] That means any packet
+ sent to any of those addresses is looped back. The address 127.0.0.1 is
+ the standard address for IPv4 loopback traffic; the rest are not supported
+ by all operating systems. However, they can be used to set up multiple
+ server applications on the host, all listening on the same port number.
+ The IPv6 standard assigns only a single address for loopback: ::1. The
+ resolution of the name localhost to one or more IP addresses is normally
+ configured by the following lines in the operating system's hosts
+ file:IPv4 network standards reserve the entire address block 127.0.0.0/8
+ (more than 16 million addresses) for loopback purposes.[2] That means any
+ packet sent to any of those addresses is looped back. The address
+ 127.0.0.1 is the standard address for IPv4 loopback traffic; the rest are
+ not supported by all operating systems. However, they can be used to set
+ up multiple server applications on the host, all listening on the same
+ port number. The IPv6 standard assigns only a single address for loopback:
+ ::1. The resolution of the name localhost to one or more IP addresses is
+ normally configured by the following lines in the operating system's hosts
+ file:
+ The name localhost is reserved for loopback purposes by RFC 6761
+ (Special-Use Domain Names),[4] which achieved the Proposed Standard
+ maturity level in February 2013. The standard sets forth a number of
+ special considerations governing the use of the name in the Domain Name
+ System:
+ The processing of any packet sent to a loopback address, is implemented in
+ the link layer of the TCP/IP stack. Such packets are never passed to any
+ network interface controller (NIC) or hardware device driver and must not
+ appear outside of a computing system, or be routed by any router. This
+ permits software testing and local services in the absence of any hardware
+ network interfaces.
+ The releases of the MySQL database differentiate between the use of the
+ hostname localhost and the use of the addresses 127.0.0.1 and ::1.[7] When
+ using localhost as the destination in a client connector interface of an
+ application, the MySQL application programming interface connects to the
+ database using a Unix domain socket, while a TCP connection via the
+ loopback interface requires the direct use of the explicit address.
+
+ The local loopback mechanism may be used to run a network service on a
+ host without requiring a physical network interface, or without making the
+ service accessible from the networks the computer may be connected to. For
+ example, a locally installed website may be accessed from a Web browser by
+ the URL http://localhost to display its home page. The name localhost
+ normally resolves to the IPv4 loopback address 127.0.0.1, and to the IPv6
+ loopback address ::1.
+
+ IPv4 network standards reserve the entire address block 127.0.0.0/8 (more
+ than 16 million addresses) for loopback purposes.[2] That means any packet
+ sent to any of those addresses is looped back. The address 127.0.0.1 is
+ the standard address for IPv4 loopback traffic; the rest are not supported
+ by all operating systems. However, they can be used to set up multiple
+ server applications on the host, all listening on the same port number.
+ The IPv6 standard assigns only a single address for loopback: ::1. The
+ resolution of the name localhost to one or more IP addresses is normally
+ configured by the following lines in the operating system's hosts
+ file:IPv4 network standards reserve the entire address block 127.0.0.0/8
+ (more than 16 million addresses) for loopback purposes.[2] That means any
+ packet sent to any of those addresses is looped back. The address
+ 127.0.0.1 is the standard address for IPv4 loopback traffic; the rest are
+ not supported by all operating systems. However, they can be used to set
+ up multiple server applications on the host, all listening on the same
+ port number. The IPv6 standard assigns only a single address for loopback:
+ ::1. The resolution of the name localhost to one or more IP addresses is
+ normally configured by the following lines in the operating system's hosts
+ file:
+ The name localhost is reserved for loopback purposes by RFC 6761
+ (Special-Use Domain Names),[4] which achieved the Proposed Standard
+ maturity level in February 2013. The standard sets forth a number of
+ special considerations governing the use of the name in the Domain Name
+ System:
+ The processing of any packet sent to a loopback address, is implemented in
+ the link layer of the TCP/IP stack. Such packets are never passed to any
+ network interface controller (NIC) or hardware device driver and must not
+ appear outside of a computing system, or be routed by any router. This
+ permits software testing and local services in the absence of any hardware
+ network interfaces.
+ The releases of the MySQL database differentiate between the use of the
+ hostname localhost and the use of the addresses 127.0.0.1 and ::1.[7] When
+ using localhost as the destination in a client connector interface of an
+ application, the MySQL application programming interface connects to the
+ database using a Unix domain socket, while a TCP connection via the
+ loopback interface requires the direct use of the explicit address.
+
+ The local loopback mechanism may be used to run a network service on a
+ host without requiring a physical network interface, or without making the
+ service accessible from the networks the computer may be connected to. For
+ example, a locally installed website may be accessed from a Web browser by
+ the URL http://localhost to display its home page. The name localhost
+ normally resolves to the IPv4 loopback address 127.0.0.1, and to the IPv6
+ loopback address ::1.
+
+ IPv4 network standards reserve the entire address block 127.0.0.0/8 (more
+ than 16 million addresses) for loopback purposes.[2] That means any packet
+ sent to any of those addresses is looped back. The address 127.0.0.1 is
+ the standard address for IPv4 loopback traffic; the rest are not supported
+ by all operating systems. However, they can be used to set up multiple
+ server applications on the host, all listening on the same port number.
+ The IPv6 standard assigns only a single address for loopback: ::1. The
+ resolution of the name localhost to one or more IP addresses is normally
+ configured by the following lines in the operating system's hosts
+ file:IPv4 network standards reserve the entire address block 127.0.0.0/8
+ (more than 16 million addresses) for loopback purposes.[2] That means any
+ packet sent to any of those addresses is looped back. The address
+ 127.0.0.1 is the standard address for IPv4 loopback traffic; the rest are
+ not supported by all operating systems. However, they can be used to set
+ up multiple server applications on the host, all listening on the same
+ port number. The IPv6 standard assigns only a single address for loopback:
+ ::1. The resolution of the name localhost to one or more IP addresses is
+ normally configured by the following lines in the operating system's hosts
+ file:
+ The name localhost is reserved for loopback purposes by RFC 6761
+ (Special-Use Domain Names),[4] which achieved the Proposed Standard
+ maturity level in February 2013. The standard sets forth a number of
+ special considerations governing the use of the name in the Domain Name
+ System:
+ The processing of any packet sent to a loopback address, is implemented in
+ the link layer of the TCP/IP stack. Such packets are never passed to any
+ network interface controller (NIC) or hardware device driver and must not
+ appear outside of a computing system, or be routed by any router. This
+ permits software testing and local services in the absence of any hardware
+ network interfaces.
+ The releases of the MySQL database differentiate between the use of the
+ hostname localhost and the use of the addresses 127.0.0.1 and ::1.[7] When
+ using localhost as the destination in a client connector interface of an
+ application, the MySQL application programming interface connects to the
+ database using a Unix domain socket, while a TCP connection via the
+ loopback interface requires the direct use of the explicit address.
+
+ The local loopback mechanism may be used to run a network service on a
+ host without requiring a physical network interface, or without making the
+ service accessible from the networks the computer may be connected to. For
+ example, a locally installed website may be accessed from a Web browser by
+ the URL http://localhost to display its home page. The name localhost
+ normally resolves to the IPv4 loopback address 127.0.0.1, and to the IPv6
+ loopback address ::1.
+
+ IPv4 network standards reserve the entire address block 127.0.0.0/8 (more
+ than 16 million addresses) for loopback purposes.[2] That means any packet
+ sent to any of those addresses is looped back. The address 127.0.0.1 is
+ the standard address for IPv4 loopback traffic; the rest are not supported
+ by all operating systems. However, they can be used to set up multiple
+ server applications on the host, all listening on the same port number.
+ The IPv6 standard assigns only a single address for loopback: ::1. The
+ resolution of the name localhost to one or more IP addresses is normally
+ configured by the following lines in the operating system's hosts
+ file:IPv4 network standards reserve the entire address block 127.0.0.0/8
+ (more than 16 million addresses) for loopback purposes.[2] That means any
+ packet sent to any of those addresses is looped back. The address
+ 127.0.0.1 is the standard address for IPv4 loopback traffic; the rest are
+ not supported by all operating systems. However, they can be used to set
+ up multiple server applications on the host, all listening on the same
+ port number. The IPv6 standard assigns only a single address for loopback:
+ ::1. The resolution of the name localhost to one or more IP addresses is
+ normally configured by the following lines in the operating system's hosts
+ file:
+ The name localhost is reserved for loopback purposes by RFC 6761
+ (Special-Use Domain Names),[4] which achieved the Proposed Standard
+ maturity level in February 2013. The standard sets forth a number of
+ special considerations governing the use of the name in the Domain Name
+ System:
+ The processing of any packet sent to a loopback address, is implemented in
+ the link layer of the TCP/IP stack. Such packets are never passed to any
+ network interface controller (NIC) or hardware device driver and must not
+ appear outside of a computing system, or be routed by any router. This
+ permits software testing and local services in the absence of any hardware
+ network interfaces.
+ The releases of the MySQL database differentiate between the use of the
+ hostname localhost and the use of the addresses 127.0.0.1 and ::1.[7] When
+ using localhost as the destination in a client connector interface of an
+ application, the MySQL application programming interface connects to the
+ database using a Unix domain socket, while a TCP connection via the
+ loopback interface requires the direct use of the explicit address.
+
+ The local loopback mechanism may be used to run a network service on a
+ host without requiring a physical network interface, or without making the
+ service accessible from the networks the computer may be connected to. For
+ example, a locally installed website may be accessed from a Web browser by
+ the URL http://localhost to display its home page. The name localhost
+ normally resolves to the IPv4 loopback address 127.0.0.1, and to the IPv6
+ loopback address ::1.
+
+ IPv4 network standards reserve the entire address block 127.0.0.0/8 (more
+ than 16 million addresses) for loopback purposes.[2] That means any packet
+ sent to any of those addresses is looped back. The address 127.0.0.1 is
+ the standard address for IPv4 loopback traffic; the rest are not supported
+ by all operating systems. However, they can be used to set up multiple
+ server applications on the host, all listening on the same port number.
+ The IPv6 standard assigns only a single address for loopback: ::1. The
+ resolution of the name localhost to one or more IP addresses is normally
+ configured by the following lines in the operating system's hosts
+ file:IPv4 network standards reserve the entire address block 127.0.0.0/8
+ (more than 16 million addresses) for loopback purposes.[2] That means any
+ packet sent to any of those addresses is looped back. The address
+ 127.0.0.1 is the standard address for IPv4 loopback traffic; the rest are
+ not supported by all operating systems. However, they can be used to set
+ up multiple server applications on the host, all listening on the same
+ port number. The IPv6 standard assigns only a single address for loopback:
+ ::1. The resolution of the name localhost to one or more IP addresses is
+ normally configured by the following lines in the operating system's hosts
+ file:
+ The name localhost is reserved for loopback purposes by RFC 6761
+ (Special-Use Domain Names),[4] which achieved the Proposed Standard
+ maturity level in February 2013. The standard sets forth a number of
+ special considerations governing the use of the name in the Domain Name
+ System:
+ The processing of any packet sent to a loopback address, is implemented in
+ the link layer of the TCP/IP stack. Such packets are never passed to any
+ network interface controller (NIC) or hardware device driver and must not
+ appear outside of a computing system, or be routed by any router. This
+ permits software testing and local services in the absence of any hardware
+ network interfaces.
+ The releases of the MySQL database differentiate between the use of the
+ hostname localhost and the use of the addresses 127.0.0.1 and ::1.[7] When
+ using localhost as the destination in a client connector interface of an
+ application, the MySQL application programming interface connects to the
+ database using a Unix domain socket, while a TCP connection via the
+ loopback interface requires the direct use of the explicit address.
+
+ One notable exception to the use of the 127.0.0.0/8 addresses is their use
+ in Multiprotocol Label Switching (MPLS) traceroute error detection, in
+ which their property of not being routable provides a convenient means to
+ avoid delivery of faulty packets to end users.
+ In computer networking, localhost is a hostname that refers to the current computer used to access it. It is used to access the network services that are running on the host via the loopback network interface.
+ Using the loopback interface bypasses any local network interface hardware.
+ The local loopback mechanism may be used to run a network service on a host without requiring a physical network interface, or without making the service accessible from the networks the computer may be connected to. For example, a locally installed website may be accessed from a Web browser by the URL http://localhost to display its home page.
+ The name localhost normally resolves to the IPv4 loopback address 127.0.0.1, and to the IPv6 loopback address ::1.
+ IPv4 network standards reserve the entire address block 127.0.0.0/8 (more than 16 million addresses) for loopback purposes.[2] That means any packet sent to any of those addresses is looped back. The address 127.0.0.1 is the standard address for IPv4 loopback traffic; the rest are not supported by all operating systems. However, they can be used to set up multiple server applications on the host, all listening on the same port number. The IPv6 standard assigns only a single address for loopback: ::1.
+ The resolution of the name localhost to one or more IP addresses is normally configured by the following lines in the operating system's hosts file:
+ 127.0.0.1 localhost
+ ::1 localhost
+ The name may also be resolved by Domain Name System (DNS) servers, but queries for this name should be resolved locally, and should not be forwarded to remote name servers. In addition to the mapping of localhost to the loopback addresses (127.0.0.1 and ::1), localhost may also be mapped to other IPv4 (loopback) addresses and it is also possible to assign other, or additional, names to any loopback address. The mapping of localhost to addresses other than the designated loopback address range in the hosts file or in DNS is not guaranteed to have the desired effect, as applications may map the name internally. In the Domain Name System, the name localhost is reserved as a top-level domain name, originally set aside to avoid confusion with the hostname used for loopback purposes.[3] IETF standards prohibit domain name registrars from assigning the name localhost. The name localhost is reserved for loopback purposes by RFC 6761 (Special-Use Domain Names),[4] which achieved the Proposed Standard maturity level in February 2013. The standard sets forth a number of special considerations governing the use of the name in the Domain Name System: An IPv4 or IPv6 address query for the name localhost must always resolve to the respective loopback address, which is specified in a separate standard.
+ Applications may resolve the name to a loopback address themselves, or pass it to the local name resolver mechanisms.
+ When a name resolver receives an address (A or AAAA) query for localhost, it should return the appropriate loopback addresses, and negative responses for any other requested record types. Queries for localhost should not be sent to caching name servers.
+ To avoid burdening the Domain Name System root servers with traffic, caching name servers should never request name server records for localhost, or forward resolution to authoritative name servers.
+ DNS registrars are precluded from delegating domain names in the top-level domain localhost.
+ When authoritative name servers receive queries for 'localhost' in spite of the provisions mentioned resolve them appropriately.
+ The IPv4 loopback addresses are reserved within the IPv4 address space by the IETF "Special Use IPv4 Addresses" standard (RFC 5735).[5] The reservation can be traced back to the November 1986 "Assigned Numbers" standard (RFC 990).
+ In contrast, the IETF "IP Version 6 Addressing Architecture" standard (RFC 4291) reserves the single IPv6 loopback address ::1 within the IPv6 address space. The standard precludes the assignment of that address to any physical interface, as well as its use as the source or destination address in any packet sent to remote hosts. Any such packet that is erroneously transmitted is not supposed to be routed, and should be dropped by all routers or hosts that receive it. The processing of any packet sent to a loopback address, is implemented in the link layer of the TCP/IP stack. Such packets are never passed to any network interface controller (NIC) or hardware device driver and must not appear outside of a computing system, or be routed by any router. This permits software testing and local services in the absence of any hardware network interfaces. Looped-back packets are distinguished from any other packets traversing the TCP/IP stack only by the special IP address they were addressed to. Thus, the services that ultimately receive them respond according to the specified destination. For example, an HTTP service could route packets addressed to 127.0.0.99:80 and 127.0.0.100:80 to different Web servers, or to a single server that returns different web pages. To simplify such testing, the hosts file may be configured to provide appropriate names for each address. Packets received on a non-loopback interface with a loopback source or destination address must be dropped. Such packets are sometimes referred to as Martian packets.[6] As with any other bogus packets, they may be malicious and any problems they might cause can be avoided by applying bogon filtering. The releases of the MySQL database differentiate between the use of the hostname localhost and the use of the addresses 127.0.0.1 and ::1.[7] When using localhost as the destination in a client connector interface of an application, the MySQL application programming interface connects to the database using a Unix domain socket, while a TCP connection via the loopback interface requires the direct use of the explicit address. One notable exception to the use of the 127.0.0.0/8 addresses is their use in Multiprotocol Label Switching (MPLS) traceroute error detection, in which their property of not being routable provides a convenient means to avoid delivery of faulty packets to end users. In computer networking, localhost is a hostname that refers to the current computer used to access it. It is used to access the network services that are running on the host via the loopback network interface.
+ Using the loopback interface bypasses any local network interface hardware.
+ The local loopback mechanism may be used to run a network service on a host without requiring a physical network interface, or without making the service accessible from the networks the computer may be connected to. For example, a locally installed website may be accessed from a Web browser by the URL http://localhost to display its home page.
+ The name localhost normally resolves to the IPv4 loopback address 127.0.0.1, and to the IPv6 loopback address ::1.
+ IPv4 network standards reserve the entire address block 127.0.0.0/8 (more than 16 million addresses) for loopback purposes.[2] That means any packet sent to any of those addresses is looped back. The address 127.0.0.1 is the standard address for IPv4 loopback traffic; the rest are not supported by all operating systems. However, they can be used to set up multiple server applications on the host, all listening on the same port number. The IPv6 standard assigns only a single address for loopback: ::1.
+ The resolution of the name localhost to one or more IP addresses is normally configured by the following lines in the operating system's hosts file:
+ 127.0.0.1 localhost
+ ::1 localhost
+ The name may also be resolved by Domain Name System (DNS) servers, but queries for this name should be resolved locally, and should not be forwarded to remote name servers. In addition to the mapping of localhost to the loopback addresses (127.0.0.1 and ::1), localhost may also be mapped to other IPv4 (loopback) addresses and it is also possible to assign other, or additional, names to any loopback address. The mapping of localhost to addresses other than the designated loopback address range in the hosts file or in DNS is not guaranteed to have the desired effect, as applications may map the name internally. In the Domain Name System, the name localhost is reserved as a top-level domain name, originally set aside to avoid confusion with the hostname used for loopback purposes.[3] IETF standards prohibit domain name registrars from assigning the name localhost. The name localhost is reserved for loopback purposes by RFC 6761 (Special-Use Domain Names),[4] which achieved the Proposed Standard maturity level in February 2013. The standard sets forth a number of special considerations governing the use of the name in the Domain Name System: An IPv4 or IPv6 address query for the name localhost must always resolve to the respective loopback address, which is specified in a separate standard.
+ Applications may resolve the name to a loopback address themselves, or pass it to the local name resolver mechanisms.
+ When a name resolver receives an address (A or AAAA) query for localhost, it should return the appropriate loopback addresses, and negative responses for any other requested record types. Queries for localhost should not be sent to caching name servers.
+ To avoid burdening the Domain Name System root servers with traffic, caching name servers should never request name server records for localhost, or forward resolution to authoritative name servers.
+ DNS registrars are precluded from delegating domain names in the top-level domain localhost.
+ When authoritative name servers receive queries for 'localhost' in spite of the provisions mentioned resolve them appropriately.
+ The IPv4 loopback addresses are reserved within the IPv4 address space by the IETF "Special Use IPv4 Addresses" standard (RFC 5735).[5] The reservation can be traced back to the November 1986 "Assigned Numbers" standard (RFC 990).
+ In contrast, the IETF "IP Version 6 Addressing Architecture" standard (RFC 4291) reserves the single IPv6 loopback address ::1 within the IPv6 address space. The standard precludes the assignment of that address to any physical interface, as well as its use as the source or destination address in any packet sent to remote hosts. Any such packet that is erroneously transmitted is not supposed to be routed, and should be dropped by all routers or hosts that receive it. The processing of any packet sent to a loopback address, is implemented in the link layer of the TCP/IP stack. Such packets are never passed to any network interface controller (NIC) or hardware device driver and must not appear outside of a computing system, or be routed by any router. This permits software testing and local services in the absence of any hardware network interfaces. Looped-back packets are distinguished from any other packets traversing the TCP/IP stack only by the special IP address they were addressed to. Thus, the services that ultimately receive them respond according to the specified destination. For example, an HTTP service could route packets addressed to 127.0.0.99:80 and 127.0.0.100:80 to different Web servers, or to a single server that returns different web pages. To simplify such testing, the hosts file may be configured to provide appropriate names for each address. Packets received on a non-loopback interface with a loopback source or destination address must be dropped. Such packets are sometimes referred to as Martian packets.[6] As with any other bogus packets, they may be malicious and any problems they might cause can be avoided by applying bogon filtering. The releases of the MySQL database differentiate between the use of the hostname localhost and the use of the addresses 127.0.0.1 and ::1.[7] When using localhost as the destination in a client connector interface of an application, the MySQL application programming interface connects to the database using a Unix domain socket, while a TCP connection via the loopback interface requires the direct use of the explicit address. One notable exception to the use of the 127.0.0.0/8 addresses is their use in Multiprotocol Label Switching (MPLS) traceroute error detection, in which their property of not being routable provides a convenient means to avoid delivery of faulty packets to end users. In computer networking, localhost is a hostname that refers to the current computer used to access it. It is used to access the network services that are running on the host via the loopback network interface.
+ Using the loopback interface bypasses any local network interface hardware.
+ The local loopback mechanism may be used to run a network service on a host without requiring a physical network interface, or without making the service accessible from the networks the computer may be connected to. For example, a locally installed website may be accessed from a Web browser by the URL http://localhost to display its home page.
+ The name localhost normally resolves to the IPv4 loopback address 127.0.0.1, and to the IPv6 loopback address ::1.
+ IPv4 network standards reserve the entire address block 127.0.0.0/8 (more than 16 million addresses) for loopback purposes.[2] That means any packet sent to any of those addresses is looped back. The address 127.0.0.1 is the standard address for IPv4 loopback traffic; the rest are not supported by all operating systems. However, they can be used to set up multiple server applications on the host, all listening on the same port number. The IPv6 standard assigns only a single address for loopback: ::1.
+ The resolution of the name localhost to one or more IP addresses is normally configured by the following lines in the operating system's hosts file:
+ 127.0.0.1 localhost
+ ::1 localhost
+ The name may also be resolved by Domain Name System (DNS) servers, but queries for this name should be resolved locally, and should not be forwarded to remote name servers. In addition to the mapping of localhost to the loopback addresses (127.0.0.1 and ::1), localhost may also be mapped to other IPv4 (loopback) addresses and it is also possible to assign other, or additional, names to any loopback address. The mapping of localhost to addresses other than the designated loopback address range in the hosts file or in DNS is not guaranteed to have the desired effect, as applications may map the name internally. In the Domain Name System, the name localhost is reserved as a top-level domain name, originally set aside to avoid confusion with the hostname used for loopback purposes.[3] IETF standards prohibit domain name registrars from assigning the name localhost. The name localhost is reserved for loopback purposes by RFC 6761 (Special-Use Domain Names),[4] which achieved the Proposed Standard maturity level in February 2013. The standard sets forth a number of special considerations governing the use of the name in the Domain Name System: An IPv4 or IPv6 address query for the name localhost must always resolve to the respective loopback address, which is specified in a separate standard.
+ Applications may resolve the name to a loopback address themselves, or pass it to the local name resolver mechanisms.
+ When a name resolver receives an address (A or AAAA) query for localhost, it should return the appropriate loopback addresses, and negative responses for any other requested record types. Queries for localhost should not be sent to caching name servers.
+ To avoid burdening the Domain Name System root servers with traffic, caching name servers should never request name server records for localhost, or forward resolution to authoritative name servers.
+ DNS registrars are precluded from delegating domain names in the top-level domain localhost.
+ When authoritative name servers receive queries for 'localhost' in spite of the provisions mentioned resolve them appropriately.
+ The IPv4 loopback addresses are reserved within the IPv4 address space by the IETF "Special Use IPv4 Addresses" standard (RFC 5735).[5] The reservation can be traced back to the November 1986 "Assigned Numbers" standard (RFC 990).
+ In contrast, the IETF "IP Version 6 Addressing Architecture" standard (RFC 4291) reserves the single IPv6 loopback address ::1 within the IPv6 address space. The standard precludes the assignment of that address to any physical interface, as well as its use as the source or destination address in any packet sent to remote hosts. Any such packet that is erroneously transmitted is not supposed to be routed, and should be dropped by all routers or hosts that receive it. The processing of any packet sent to a loopback address, is implemented in the link layer of the TCP/IP stack. Such packets are never passed to any network interface controller (NIC) or hardware device driver and must not appear outside of a computing system, or be routed by any router. This permits software testing and local services in the absence of any hardware network interfaces. Looped-back packets are distinguished from any other packets traversing the TCP/IP stack only by the special IP address they were addressed to. Thus, the services that ultimately receive them respond according to the specified destination. For example, an HTTP service could route packets addressed to 127.0.0.99:80 and 127.0.0.100:80 to different Web servers, or to a single server that returns different web pages. To simplify such testing, the hosts file may be configured to provide appropriate names for each address. Packets received on a non-loopback interface with a loopback source or destination address must be dropped. Such packets are sometimes referred to as Martian packets.[6] As with any other bogus packets, they may be malicious and any problems they might cause can be avoided by applying bogon filtering. The releases of the MySQL database differentiate between the use of the hostname localhost and the use of the addresses 127.0.0.1 and ::1.[7] When using localhost as the destination in a client connector interface of an application, the MySQL application programming interface connects to the database using a Unix domain socket, while a TCP connection via the loopback interface requires the direct use of the explicit address. One notable exception to the use of the 127.0.0.0/8 addresses is their use in Multiprotocol Label Switching (MPLS) traceroute error detection, in which their property of not being routable provides a convenient means to avoid delivery of faulty packets to end users.
+ The local loopback mechanism may be used to run a network service on a
+ host without requiring a physical network interface, or without making the
+ service accessible from the networks the computer may be connected to. For
+ example, a locally installed website may be accessed from a Web browser by
+ the URL http://localhost to display its home page. The name localhost
+ normally resolves to the IPv4 loopback address 127.0.0.1, and to the IPv6
+ loopback address ::1.
+
+ IPv4 network standards reserve the entire address block 127.0.0.0/8 (more
+ than 16 million addresses) for loopback purposes.[2] That means any packet
+ sent to any of those addresses is looped back. The address 127.0.0.1 is
+ the standard address for IPv4 loopback traffic; the rest are not supported
+ by all operating systems. However, they can be used to set up multiple
+ server applications on the host, all listening on the same port number.
+ The IPv6 standard assigns only a single address for loopback: ::1. The
+ resolution of the name localhost to one or more IP addresses is normally
+ configured by the following lines in the operating system's hosts
+ file:IPv4 network standards reserve the entire address block 127.0.0.0/8
+ (more than 16 million addresses) for loopback purposes.[2] That means any
+ packet sent to any of those addresses is looped back. The address
+ 127.0.0.1 is the standard address for IPv4 loopback traffic; the rest are
+ not supported by all operating systems. However, they can be used to set
+ up multiple server applications on the host, all listening on the same
+ port number. The IPv6 standard assigns only a single address for loopback:
+ ::1. The resolution of the name localhost to one or more IP addresses is
+ normally configured by the following lines in the operating system's hosts
+ file:
+ The name localhost is reserved for loopback purposes by RFC 6761
+ (Special-Use Domain Names),[4] which achieved the Proposed Standard
+ maturity level in February 2013. The standard sets forth a number of
+ special considerations governing the use of the name in the Domain Name
+ System:
+ The processing of any packet sent to a loopback address, is implemented in
+ the link layer of the TCP/IP stack. Such packets are never passed to any
+ network interface controller (NIC) or hardware device driver and must not
+ appear outside of a computing system, or be routed by any router. This
+ permits software testing and local services in the absence of any hardware
+ network interfaces.
+ The releases of the MySQL database differentiate between the use of the
+ hostname localhost and the use of the addresses 127.0.0.1 and ::1.[7] When
+ using localhost as the destination in a client connector interface of an
+ application, the MySQL application programming interface connects to the
+ database using a Unix domain socket, while a TCP connection via the
+ loopback interface requires the direct use of the explicit address.
+
+ The local loopback mechanism may be used to run a network service on a
+ host without requiring a physical network interface, or without making the
+ service accessible from the networks the computer may be connected to. For
+ example, a locally installed website may be accessed from a Web browser by
+ the URL http://localhost to display its home page. The name localhost
+ normally resolves to the IPv4 loopback address 127.0.0.1, and to the IPv6
+ loopback address ::1.
+
+ IPv4
+ network
+ standards reserve the entire address block
+ 127.0.0.0/8 (more than 16 million addresses) for loopback purposes.[2]
+ That means any packet sent to any of those addresses is looped back. The
+ address 127.0.0.1 is the standard address for IPv4
+ loopback
+ traffic; the rest are not supported by all operating systems. However,
+ they can be used to set up multiple server applications on the host, all
+ listening on the same port number. The IPv6 standard assigns only a single
+ address for loopback: ::1. The resolution of the name localhost to one or
+ more IP addresses is normally configured by the following lines in the
+ operating system's hosts file:IPv4 network standards reserve the entire
+ address block 127.0.0.0/8 (more than 16 million addresses) for loopback
+ purposes.[2] That means any packet sent
+ to any of those addresses is looped back. The address 127.0.0.1 is the
+ standard address for IPv4 loopback traffic; the rest are not supported by
+ all operating systems. However, they can be used to set up multiple server
+ applications on the host, all listening on the same port number. The IPv6
+ standard assigns only a single address for loopback: ::1. The resolution
+ of the name localhost to one or more IP addresses is normally configured
+ by the following lines in the operating system's hosts file:
+ The name localhost is reserved for loopback purposes by RFC 6761
+ (Special-Use Domain Names),[4] which achieved the Proposed Standard
+ maturity level in February 2013. The standard sets forth a number of
+ special considerations governing the use of the name in the Domain Name
+ System:
+ The processing of any packet sent to a loopback address, is implemented in
+ the link layer of the TCP/IP stack. Such packets are never passed to any
+ network interface controller (NIC) or hardware device driver and must not
+ appear outside of a computing system, or be routed by any router. This
+ permits software testing and local services in the absence of any hardware
+ network interfaces.
+ The releases of the
+ MySQL database
+ differentiate between the use of the hostname localhost and the use of the
+ addresses 127.0.0.1 and ::1.[7] When using localhost as the destination in
+ a client connector interface of an application, the MySQL application
+ programming interface connects to the database using a Unix domain socket,
+ while a TCP connection via the loopback interface requires the direct use
+ of the explicit address.
+ The local loopback mechanism may be used to run a network service on a
+ host without requiring a physical network interface, or without making the
+ service accessible from the networks the computer may be connected to. For
+ example, a locally installed website may be accessed from a Web browser by
+ the URL http://localhost to display its home page. The name localhost
+ normally resolves to the IPv4 loopback address 127.0.0.1, and to the IPv6
+ loopback address ::1.
+
+ IPv4
+ network
+ standards reserve the entire address block
+ 127.0.0.0/8 (more than 16 million addresses) for loopback purposes.[2]
+ That means any packet sent to any of those addresses is looped back. The
+ address 127.0.0.1 is the standard address for IPv4
+ loopback
+ traffic; the rest are not supported by all operating systems. However,
+ they can be used to set up multiple server applications on the host, all
+ listening on the same port number. The IPv6 standard assigns only a single
+ address for loopback: ::1. The resolution of the name localhost to one or
+ more IP addresses is normally configured by the following lines in the
+ operating system's hosts file:IPv4 network standards reserve the entire
+ address block 127.0.0.0/8 (more than 16 million addresses) for loopback
+ purposes.[2] That means any packet sent
+ to any of those addresses is looped back. The address 127.0.0.1 is the
+ standard address for IPv4 loopback traffic; the rest are not supported by
+ all operating systems. However, they can be used to set up multiple server
+ applications on the host, all listening on the same port number. The IPv6
+ standard assigns only a single address for loopback: ::1. The resolution
+ of the name localhost to one or more IP addresses is normally configured
+ by the following lines in the operating system's hosts file:
+ The name localhost is reserved for loopback purposes by RFC 6761
+ (Special-Use Domain Names),[4] which achieved the Proposed Standard
+ maturity level in February 2013. The standard sets forth a number of
+ special considerations governing the use of the name in the Domain Name
+ System:
+ The processing of any packet sent to a loopback address, is implemented in
+ the link layer of the TCP/IP stack. Such packets are never passed to any
+ network interface controller (NIC) or hardware device driver and must not
+ appear outside of a computing system, or be routed by any router. This
+ permits software testing and local services in the absence of any hardware
+ network interfaces.
+ The releases of the
+ MySQL database
+ differentiate between the use of the hostname localhost and the use of the
+ addresses 127.0.0.1 and ::1.[7] When using localhost as the destination in
+ a client connector interface of an application, the MySQL application
+ programming interface connects to the database using a Unix domain socket,
+ while a TCP connection via the loopback interface requires the direct use
+ of the explicit address.
+ The local loopback mechanism may be used to run a network service on a
+ host without requiring a physical network interface, or without making the
+ service accessible from the networks the computer may be connected to. For
+ example, a locally installed website may be accessed from a Web browser by
+ the URL http://localhost to display its home page. The name localhost
+ normally resolves to the IPv4 loopback address 127.0.0.1, and to the
+ IPv6
+ loopback address ::1.
+ IPv4
+ network
+ standards reserve the entire address block
+ 127.0.0.0/8 (more than 16 million addresses) for loopback purposes.[2]
+ That means any packet sent to any of those addresses is looped back. The
+ address 127.0.0.1 is the standard address for IPv4
+ loopback
+ traffic; the rest are not supported by all operating systems. However,
+ they can be used to set up multiple server applications on the host, all
+ listening on the same port number. The IPv6 standard assigns only a single
+ address for loopback: ::1. The resolution of the name localhost to one or
+ more IP addresses is normally configured by the following lines in the
+ operating system's hosts file:IPv4 network standards reserve the entire
+ address block 127.0.0.0/8 (more than 16 million addresses) for loopback
+ purposes.[2] That means any packet sent
+ to any of those addresses is looped back. The address 127.0.0.1 is the
+ standard address for IPv4 loopback traffic; the rest are not supported by
+ all operating systems. However, they can be used to set up multiple server
+ applications on the host, all listening on the same port number. The IPv6
+ standard assigns only a single address for loopback: ::1. The resolution
+ of the name localhost to one or more IP addresses is normally configured
+ by the following lines in the operating system's hosts file:
+ The name localhost is reserved for loopback purposes by RFC 6761
+ (Special-Use Domain Names),[4] which achieved the Proposed Standard
+ maturity level in February 2013. The standard sets forth a number of
+ special considerations governing the use of the name in the Domain Name
+ System: Localhost
+ Loopback
+
+ 127.0.0.1 localhost
+ ::1 localhost
+ 127.0.0.1 localhost
+ ::1 localhost
+
+ The name may also be resolved by Domain Name System (DNS) servers, but
+ queries for this name should be resolved locally, and should not be
+ forwarded to remote name servers.
+
+ In addition to the mapping of localhost to the loopback addresses
+ (127.0.0.1 and ::1), localhost may also be mapped to other IPv4 (loopback)
+ addresses and it is also possible to assign other, or additional, names to
+ any loopback address. The mapping of localhost to addresses other than the
+ designated loopback address range in the hosts file or in DNS is not
+ guaranteed to have the desired effect, as applications may map the name
+ internally.
+
+ In the Domain Name System, the name localhost is reserved as a top-level
+ domain name, originally set aside to avoid confusion with the hostname
+ used for loopback purposes.[3] IETF standards prohibit domain name
+ registrars from assigning the name localhost.
+ IETF standards
+
+
+
+
+ An IPv4 or IPv6 address query for the name localhost must always resolve
+ to the respective loopback address, which is specified in a separate
+ standard. Applications may resolve the name to a loopback address
+ themselves, or pass it to the local name resolver mechanisms. When a name
+ resolver receives an address (A or AAAA) query for localhost, it should
+ return the appropriate loopback addresses, and negative responses for any
+ other requested record types. Queries for localhost should not be sent to
+ caching name servers. To avoid burdening the Domain Name System root
+ servers with traffic, caching name servers should never request name
+ server records for localhost, or forward resolution to authoritative name
+ servers. DNS registrars are precluded from delegating domain names in the
+ top-level domain localhost. When authoritative name servers receive
+ queries for 'localhost' in spite of the provisions mentioned resolve them
+ appropriately. The IPv4 loopback addresses are reserved within the IPv4
+ address space by the IETF "Special Use IPv4 Addresses" standard (RFC
+ 5735).[5] The reservation can be traced back to the November 1986
+ "Assigned Numbers" standard (RFC 990).
+
+
+ In contrast, the IETF "IP Version 6 Addressing Architecture" standard (RFC
+ 4291) reserves the single IPv6 loopback address ::1 within the IPv6
+ address space. The standard precludes the assignment of that address to
+ any physical interface, as well as its use as the source or destination
+ address in any packet sent to remote hosts. Any such packet that is
+ erroneously transmitted is not supposed to be routed, and should be
+ dropped by all routers or hosts that receive it.
+ Packet processing
+
+ Looped-back packets are distinguished from any other packets traversing
+ the TCP/IP stack only by the special IP address they were addressed to.
+ Thus, the services that ultimately receive them respond according to the
+ specified destination. For example, an HTTP service could route packets
+ addressed to 127.0.0.99:80 and 127.0.0.100:80 to different Web servers, or
+ to a single server that returns different web pages. To simplify such
+ testing, the hosts file may be configured to provide appropriate names for
+ each address.
+
+ Packets received on a non-loopback interface with a loopback source or
+ destination address must be dropped. Such packets are sometimes referred
+ to as Martian packets.[6] As with any other bogus packets, they may be
+ malicious and any problems they might cause can be avoided by applying
+ bogon filtering.
+ Special cases
+
+
+ One notable exception to the use of the 127.0.0.0/8 addresses is their use
+ in Multiprotocol Label Switching (MPLS) traceroute error detection, in
+ which their property of not being routable provides a convenient means to
+ avoid delivery of faulty packets to end users.
+ Localhost
+ Loopback
+
+ 127.0.0.1 localhost
+ ::1 localhost
+ 127.0.0.1 localhost
+ ::1 localhost
+
+ The name may also be resolved by Domain Name System (DNS) servers, but
+ queries for this name should be resolved locally, and should not be
+ forwarded to remote name servers.
+
+ In addition to the mapping of localhost to the loopback addresses
+ (127.0.0.1 and ::1), localhost may also be mapped to other IPv4 (loopback)
+ addresses and it is also possible to assign other, or additional, names to
+ any loopback address. The mapping of localhost to addresses other than the
+ designated loopback address range in the hosts file or in DNS is not
+ guaranteed to have the desired effect, as applications may map the name
+ internally.
+
+ In the Domain Name System, the name localhost is reserved as a top-level
+ domain name, originally set aside to avoid confusion with the hostname
+ used for loopback purposes.[3] IETF standards prohibit domain name
+ registrars from assigning the name localhost.
+ IETF standards
+
+
+
+
+ An IPv4 or IPv6 address query for the name localhost must always resolve
+ to the respective loopback address, which is specified in a separate
+ standard. Applications may resolve the name to a loopback address
+ themselves, or pass it to the local name resolver mechanisms. When a name
+ resolver receives an address (A or AAAA) query for localhost, it should
+ return the appropriate loopback addresses, and negative responses for any
+ other requested record types. Queries for localhost should not be sent to
+ caching name servers. To avoid burdening the Domain Name System root
+ servers with traffic, caching name servers should never request name
+ server records for localhost, or forward resolution to authoritative name
+ servers. DNS registrars are precluded from delegating domain names in the
+ top-level domain localhost. When authoritative name servers receive
+ queries for 'localhost' in spite of the provisions mentioned resolve them
+ appropriately. The IPv4 loopback addresses are reserved within the IPv4
+ address space by the IETF "Special Use IPv4 Addresses" standard (RFC
+ 5735).[5] The reservation can be traced back to the November 1986
+ "Assigned Numbers" standard (RFC 990).
+
+
+ In contrast, the IETF "IP Version 6 Addressing Architecture" standard (RFC
+ 4291) reserves the single IPv6 loopback address ::1 within the IPv6
+ address space. The standard precludes the assignment of that address to
+ any physical interface, as well as its use as the source or destination
+ address in any packet sent to remote hosts. Any such packet that is
+ erroneously transmitted is not supposed to be routed, and should be
+ dropped by all routers or hosts that receive it.
+ Packet processing
+
+ Looped-back packets are distinguished from any other packets traversing
+ the TCP/IP stack only by the special IP address they were addressed to.
+ Thus, the services that ultimately receive them respond according to the
+ specified destination. For example, an HTTP service could route packets
+ addressed to 127.0.0.99:80 and 127.0.0.100:80 to different Web servers, or
+ to a single server that returns different web pages. To simplify such
+ testing, the hosts file may be configured to provide appropriate names for
+ each address.
+
+ Packets received on a non-loopback interface with a loopback source or
+ destination address must be dropped. Such packets are sometimes referred
+ to as Martian packets.[6] As with any other bogus packets, they may be
+ malicious and any problems they might cause can be avoided by applying
+ bogon filtering.
+ Special cases
+
+
+ One notable exception to the use of the 127.0.0.0/8 addresses is their use
+ in Multiprotocol Label Switching (MPLS) traceroute error detection, in
+ which their property of not being routable provides a convenient means to
+ avoid delivery of faulty packets to end users.
+ Localhost
+ Loopback
+
+ 127.0.0.1 localhost
+ ::1 localhost
+ 127.0.0.1 localhost
+ ::1 localhost
+
+ The name may also be resolved by Domain Name System (DNS) servers, but
+ queries for this name should be resolved locally, and should not be
+ forwarded to remote name servers.
+
+ In addition to the mapping of localhost to the loopback addresses
+ (127.0.0.1 and ::1), localhost may also be mapped to other IPv4 (loopback)
+ addresses and it is also possible to assign other, or additional, names to
+ any loopback address. The mapping of localhost to addresses other than the
+ designated loopback address range in the hosts file or in DNS is not
+ guaranteed to have the desired effect, as applications may map the name
+ internally.
+
+ In the Domain Name System, the name localhost is reserved as a top-level
+ domain name, originally set aside to avoid confusion with the hostname
+ used for loopback purposes.[3] IETF standards prohibit domain name
+ registrars from assigning the name localhost.
+ IETF standards
+
+
+
+
+ An IPv4 or IPv6 address query for the name localhost must always resolve
+ to the respective loopback address, which is specified in a separate
+ standard. Applications may resolve the name to a loopback address
+ themselves, or pass it to the local name resolver mechanisms. When a name
+ resolver receives an address (A or AAAA) query for localhost, it should
+ return the appropriate loopback addresses, and negative responses for any
+ other requested record types. Queries for localhost should not be sent to
+ caching name servers. To avoid burdening the Domain Name System root
+ servers with traffic, caching name servers should never request name
+ server records for localhost, or forward resolution to authoritative name
+ servers. DNS registrars are precluded from delegating domain names in the
+ top-level domain localhost. When authoritative name servers receive
+ queries for 'localhost' in spite of the provisions mentioned resolve them
+ appropriately. The IPv4 loopback addresses are reserved within the IPv4
+ address space by the IETF "Special Use IPv4 Addresses" standard (RFC
+ 5735).[5] The reservation can be traced back to the November 1986
+ "Assigned Numbers" standard (RFC 990).
+
+
+ In contrast, the IETF "IP Version 6 Addressing Architecture" standard (RFC
+ 4291) reserves the single IPv6 loopback address ::1 within the IPv6
+ address space. The standard precludes the assignment of that address to
+ any physical interface, as well as its use as the source or destination
+ address in any packet sent to remote hosts. Any such packet that is
+ erroneously transmitted is not supposed to be routed, and should be
+ dropped by all routers or hosts that receive it.
+ Packet processing
+
+ Looped-back packets are distinguished from any other packets traversing
+ the TCP/IP stack only by the special IP address they were addressed to.
+ Thus, the services that ultimately receive them respond according to the
+ specified destination. For example, an HTTP service could route packets
+ addressed to 127.0.0.99:80 and 127.0.0.100:80 to different Web servers, or
+ to a single server that returns different web pages. To simplify such
+ testing, the hosts file may be configured to provide appropriate names for
+ each address.
+
+ Packets received on a non-loopback interface with a loopback source or
+ destination address must be dropped. Such packets are sometimes referred
+ to as Martian packets.[6] As with any other bogus packets, they may be
+ malicious and any problems they might cause can be avoided by applying
+ bogon filtering.
+ Special cases
+
+
+ One notable exception to the use of the 127.0.0.0/8 addresses is their use
+ in Multiprotocol Label Switching (MPLS) traceroute error detection, in
+ which their property of not being routable provides a convenient means to
+ avoid delivery of faulty packets to end users.
+ Localhost
+ Loopback
+
+ 127.0.0.1 localhost
+ ::1 localhost
+ 127.0.0.1 localhost
+ ::1 localhost
+
+ The name may also be resolved by Domain Name System (DNS) servers, but
+ queries for this name should be resolved locally, and should not be
+ forwarded to remote name servers.
+
+ In addition to the mapping of localhost to the loopback addresses
+ (127.0.0.1 and ::1), localhost may also be mapped to other IPv4 (loopback)
+ addresses and it is also possible to assign other, or additional, names to
+ any loopback address. The mapping of localhost to addresses other than the
+ designated loopback address range in the hosts file or in DNS is not
+ guaranteed to have the desired effect, as applications may map the name
+ internally.
+
+ In the Domain Name System, the name localhost is reserved as a top-level
+ domain name, originally set aside to avoid confusion with the hostname
+ used for loopback purposes.[3] IETF standards prohibit domain name
+ registrars from assigning the name localhost.
+ IETF standards
+
+
+
+
+ An IPv4 or IPv6 address query for the name localhost must always resolve
+ to the respective loopback address, which is specified in a separate
+ standard. Applications may resolve the name to a loopback address
+ themselves, or pass it to the local name resolver mechanisms. When a name
+ resolver receives an address (A or AAAA) query for localhost, it should
+ return the appropriate loopback addresses, and negative responses for any
+ other requested record types. Queries for localhost should not be sent to
+ caching name servers. To avoid burdening the Domain Name System root
+ servers with traffic, caching name servers should never request name
+ server records for localhost, or forward resolution to authoritative name
+ servers. DNS registrars are precluded from delegating domain names in the
+ top-level domain localhost. When authoritative name servers receive
+ queries for 'localhost' in spite of the provisions mentioned resolve them
+ appropriately. The IPv4 loopback addresses are reserved within the IPv4
+ address space by the IETF "Special Use IPv4 Addresses" standard (RFC
+ 5735).[5] The reservation can be traced back to the November 1986
+ "Assigned Numbers" standard (RFC 990).
+
+
+ In contrast, the IETF "IP Version 6 Addressing Architecture" standard (RFC
+ 4291) reserves the single IPv6 loopback address ::1 within the IPv6
+ address space. The standard precludes the assignment of that address to
+ any physical interface, as well as its use as the source or destination
+ address in any packet sent to remote hosts. Any such packet that is
+ erroneously transmitted is not supposed to be routed, and should be
+ dropped by all routers or hosts that receive it.
+ Packet processing
+
+ Looped-back packets are distinguished from any other packets traversing
+ the TCP/IP stack only by the special IP address they were addressed to.
+ Thus, the services that ultimately receive them respond according to the
+ specified destination. For example, an HTTP service could route packets
+ addressed to 127.0.0.99:80 and 127.0.0.100:80 to different Web servers, or
+ to a single server that returns different web pages. To simplify such
+ testing, the hosts file may be configured to provide appropriate names for
+ each address.
+
+ Packets received on a non-loopback interface with a loopback source or
+ destination address must be dropped. Such packets are sometimes referred
+ to as Martian packets.[6] As with any other bogus packets, they may be
+ malicious and any problems they might cause can be avoided by applying
+ bogon filtering.
+ Special cases
+
+
+ One notable exception to the use of the 127.0.0.0/8 addresses is their use
+ in Multiprotocol Label Switching (MPLS) traceroute error detection, in
+ which their property of not being routable provides a convenient means to
+ avoid delivery of faulty packets to end users.
+ Localhost
+ Loopback
+
+ 127.0.0.1 localhost
+ ::1 localhost
+ 127.0.0.1 localhost
+ ::1 localhost
+
+ The name may also be resolved by Domain Name System (DNS) servers, but
+ queries for this name should be resolved locally, and should not be
+ forwarded to remote name servers.
+
+ In addition to the mapping of localhost to the loopback addresses
+ (127.0.0.1 and ::1), localhost may also be mapped to other IPv4 (loopback)
+ addresses and it is also possible to assign other, or additional, names to
+ any loopback address. The mapping of localhost to addresses other than the
+ designated loopback address range in the hosts file or in DNS is not
+ guaranteed to have the desired effect, as applications may map the name
+ internally.
+
+ In the Domain Name System, the name localhost is reserved as a top-level
+ domain name, originally set aside to avoid confusion with the hostname
+ used for loopback purposes.[3] IETF standards prohibit domain name
+ registrars from assigning the name localhost.
+ IETF standards
+
+
+
+
+ An IPv4 or IPv6 address query for the name localhost must always resolve
+ to the respective loopback address, which is specified in a separate
+ standard. Applications may resolve the name to a loopback address
+ themselves, or pass it to the local name resolver mechanisms. When a name
+ resolver receives an address (A or AAAA) query for localhost, it should
+ return the appropriate loopback addresses, and negative responses for any
+ other requested record types. Queries for localhost should not be sent to
+ caching name servers. To avoid burdening the Domain Name System root
+ servers with traffic, caching name servers should never request name
+ server records for localhost, or forward resolution to authoritative name
+ servers. DNS registrars are precluded from delegating domain names in the
+ top-level domain localhost. When authoritative name servers receive
+ queries for 'localhost' in spite of the provisions mentioned resolve them
+ appropriately. The IPv4 loopback addresses are reserved within the IPv4
+ address space by the IETF "Special Use IPv4 Addresses" standard (RFC
+ 5735).[5] The reservation can be traced back to the November 1986
+ "Assigned Numbers" standard (RFC 990).
+
+
+ In contrast, the IETF "IP Version 6 Addressing Architecture" standard (RFC
+ 4291) reserves the single IPv6 loopback address ::1 within the IPv6
+ address space. The standard precludes the assignment of that address to
+ any physical interface, as well as its use as the source or destination
+ address in any packet sent to remote hosts. Any such packet that is
+ erroneously transmitted is not supposed to be routed, and should be
+ dropped by all routers or hosts that receive it.
+ Packet processing
+
+ Looped-back packets are distinguished from any other packets traversing
+ the TCP/IP stack only by the special IP address they were addressed to.
+ Thus, the services that ultimately receive them respond according to the
+ specified destination. For example, an HTTP service could route packets
+ addressed to 127.0.0.99:80 and 127.0.0.100:80 to different Web servers, or
+ to a single server that returns different web pages. To simplify such
+ testing, the hosts file may be configured to provide appropriate names for
+ each address.
+
+ Packets received on a non-loopback interface with a loopback source or
+ destination address must be dropped. Such packets are sometimes referred
+ to as Martian packets.[6] As with any other bogus packets, they may be
+ malicious and any problems they might cause can be avoided by applying
+ bogon filtering.
+ Special cases
+
+
+ One notable exception to the use of the 127.0.0.0/8 addresses is their use
+ in Multiprotocol Label Switching (MPLS) traceroute error detection, in
+ which their property of not being routable provides a convenient means to
+ avoid delivery of faulty packets to end users.
+ Localhost
+ Loopback
+
+ 127.0.0.1 localhost
+ ::1 localhost
+ 127.0.0.1 localhost
+ ::1 localhost
+
+ The name may also be resolved by Domain Name System (DNS) servers, but
+ queries for this name should be resolved locally, and should not be
+ forwarded to remote name servers.
+
+ In addition to the mapping of localhost to the loopback addresses
+ (127.0.0.1 and ::1), localhost may also be mapped to other IPv4 (loopback)
+ addresses and it is also possible to assign other, or additional, names to
+ any loopback address. The mapping of localhost to addresses other than the
+ designated loopback address range in the hosts file or in DNS is not
+ guaranteed to have the desired effect, as applications may map the name
+ internally.
+
+ In the Domain Name System, the name localhost is reserved as a top-level
+ domain name, originally set aside to avoid confusion with the hostname
+ used for loopback purposes.[3] IETF standards prohibit domain name
+ registrars from assigning the name localhost.
+ IETF standards
+
+
+
+
+ An IPv4 or IPv6 address query for the name localhost must always resolve
+ to the respective loopback address, which is specified in a separate
+ standard. Applications may resolve the name to a loopback address
+ themselves, or pass it to the local name resolver mechanisms. When a name
+ resolver receives an address (A or AAAA) query for localhost, it should
+ return the appropriate loopback addresses, and negative responses for any
+ other requested record types. Queries for localhost should not be sent to
+ caching name servers. To avoid burdening the Domain Name System root
+ servers with traffic, caching name servers should never request name
+ server records for localhost, or forward resolution to authoritative name
+ servers. DNS registrars are precluded from delegating domain names in the
+ top-level domain localhost. When authoritative name servers receive
+ queries for 'localhost' in spite of the provisions mentioned resolve them
+ appropriately. The IPv4 loopback addresses are reserved within the IPv4
+ address space by the IETF "Special Use IPv4 Addresses" standard (RFC
+ 5735).[5] The reservation can be traced back to the November 1986
+ "Assigned Numbers" standard (RFC 990).
+
+
+ In contrast, the IETF "IP Version 6 Addressing Architecture" standard (RFC
+ 4291) reserves the single IPv6 loopback address ::1 within the IPv6
+ address space. The standard precludes the assignment of that address to
+ any physical interface, as well as its use as the source or destination
+ address in any packet sent to remote hosts. Any such packet that is
+ erroneously transmitted is not supposed to be routed, and should be
+ dropped by all routers or hosts that receive it.
+ Packet processing
+
+ Looped-back packets are distinguished from any other packets traversing
+ the TCP/IP stack only by the special IP address they were addressed to.
+ Thus, the services that ultimately receive them respond according to the
+ specified destination. For example, an HTTP service could route packets
+ addressed to 127.0.0.99:80 and 127.0.0.100:80 to different Web servers, or
+ to a single server that returns different web pages. To simplify such
+ testing, the hosts file may be configured to provide appropriate names for
+ each address.
+
+ Packets received on a non-loopback interface with a loopback source or
+ destination address must be dropped. Such packets are sometimes referred
+ to as Martian packets.[6] As with any other bogus packets, they may be
+ malicious and any problems they might cause can be avoided by applying
+ bogon filtering.
+ Special cases
+
+
+ One notable exception to the use of the 127.0.0.0/8 addresses is their use
+ in Multiprotocol Label Switching (MPLS) traceroute error detection, in
+ which their property of not being routable provides a convenient means to
+ avoid delivery of faulty packets to end users.
+ Localhost
+ Loopback
+
+ 127.0.0.1 localhost
+ ::1 localhost
+ 127.0.0.1 localhost
+ ::1 localhost
+
+ The name may also be resolved by Domain Name System (DNS) servers, but
+ queries for this name should be resolved locally, and should not be
+ forwarded to remote name servers.
+
+ In addition to the mapping of localhost to the loopback addresses
+ (127.0.0.1 and ::1), localhost may also be mapped to other IPv4 (loopback)
+ addresses and it is also possible to assign other, or additional, names to
+ any loopback address. The mapping of localhost to addresses other than the
+ designated loopback address range in the hosts file or in DNS is not
+ guaranteed to have the desired effect, as applications may map the name
+ internally.
+
+ In the Domain Name System, the name localhost is reserved as a top-level
+ domain name, originally set aside to avoid confusion with the hostname
+ used for loopback purposes.[3] IETF standards prohibit domain name
+ registrars from assigning the name localhost.
+ IETF standards
+
+
+
+
+ An IPv4 or IPv6 address query for the name localhost must always resolve
+ to the respective loopback address, which is specified in a separate
+ standard. Applications may resolve the name to a loopback address
+ themselves, or pass it to the local name resolver mechanisms. When a name
+ resolver receives an address (A or AAAA) query for localhost, it should
+ return the appropriate loopback addresses, and negative responses for any
+ other requested record types. Queries for localhost should not be sent to
+ caching name servers. To avoid burdening the Domain Name System root
+ servers with traffic, caching name servers should never request name
+ server records for localhost, or forward resolution to authoritative name
+ servers. DNS registrars are precluded from delegating domain names in the
+ top-level domain localhost. When authoritative name servers receive
+ queries for 'localhost' in spite of the provisions mentioned resolve them
+ appropriately. The IPv4 loopback addresses are reserved within the IPv4
+ address space by the IETF "Special Use IPv4 Addresses" standard (RFC
+ 5735).[5] The reservation can be traced back to the November 1986
+ "Assigned Numbers" standard (RFC 990).
+
+
+ In contrast, the IETF "IP Version 6 Addressing Architecture" standard (RFC
+ 4291) reserves the single IPv6 loopback address ::1 within the IPv6
+ address space. The standard precludes the assignment of that address to
+ any physical interface, as well as its use as the source or destination
+ address in any packet sent to remote hosts. Any such packet that is
+ erroneously transmitted is not supposed to be routed, and should be
+ dropped by all routers or hosts that receive it.
+ Packet processing
+
+ Looped-back packets are distinguished from any other packets traversing
+ the TCP/IP stack only by the special IP address they were addressed to.
+ Thus, the services that ultimately receive them respond according to the
+ specified destination. For example, an HTTP service could route packets
+ addressed to 127.0.0.99:80 and 127.0.0.100:80 to different Web servers, or
+ to a single server that returns different web pages. To simplify such
+ testing, the hosts file may be configured to provide appropriate names for
+ each address.
+
+ Packets received on a non-loopback interface with a loopback source or
+ destination address must be dropped. Such packets are sometimes referred
+ to as Martian packets.[6] As with any other bogus packets, they may be
+ malicious and any problems they might cause can be avoided by applying
+ bogon filtering.
+ Special cases
+
+
+ One notable exception to the use of the 127.0.0.0/8 addresses is their use
+ in Multiprotocol Label Switching (MPLS) traceroute error detection, in
+ which their property of not being routable provides a convenient means to
+ avoid delivery of faulty packets to end users.
+ Localhost
+
+ Loopback
+
+ 127.0.0.1 localhost
+ ::1 localhost
+ 127.0.0.1 localhost
+ ::1 localhost
+
+ The name may also be resolved by Domain Name System (DNS) servers, but
+ queries for this name should be resolved locally, and should not be
+ forwarded to remote name servers.
+
+ In addition to the mapping of localhost to the loopback addresses
+ (127.0.0.1 and ::1), localhost may also be mapped to other IPv4 (loopback)
+ addresses and it is also possible to assign other, or additional, names to
+ any loopback address. The mapping of localhost to addresses other than the
+ designated loopback address range in the hosts file or in DNS is not
+ guaranteed to have the desired effect, as applications may map the name
+ internally.
+
+ In the Domain Name System, the name localhost is reserved as a top-level
+ domain name, originally set aside to avoid confusion with the hostname
+ used for loopback purposes.[3] IETF standards prohibit domain name
+ registrars from assigning the name localhost.
+
+
+ IETF standards
+
+
+
+
+ An IPv4 or IPv6 address query for the name localhost must always resolve
+ to the respective loopback address, which is specified in a separate
+ standard. Applications may resolve the name to a loopback address
+ themselves, or pass it to the local name resolver mechanisms. When a name
+ resolver receives an address (A or AAAA) query for localhost, it should
+ return the appropriate loopback addresses, and negative responses for any
+ other requested record types. Queries for localhost should not be sent to
+ caching name servers. To avoid burdening the Domain Name System root
+ servers with traffic, caching name servers should never request name
+ server records for localhost, or forward resolution to authoritative name
+ servers. DNS registrars are precluded from delegating domain names in the
+ top-level domain localhost. When authoritative name servers receive
+ queries for 'localhost' in spite of the provisions mentioned resolve them
+ appropriately. The IPv4 loopback addresses are reserved within the IPv4
+ address space by the IETF "Special Use IPv4 Addresses" standard (RFC
+ 5735).[5] The reservation can be traced back to the November 1986
+ "Assigned Numbers" standard (RFC 990).
+
+
+ In contrast, the IETF "IP Version 6 Addressing Architecture" standard (RFC
+ 4291) reserves the single IPv6 loopback address ::1 within the IPv6
+ address space. The standard precludes the assignment of that address to
+ any physical interface, as well as its use as the source or destination
+ address in any packet sent to remote hosts. Any such packet that is
+ erroneously transmitted is not supposed to be routed, and should be
+ dropped by all routers or hosts that receive it.
+
+
+ Packet processing
+
+ Looped-back packets are distinguished from any other packets traversing
+ the TCP/IP stack only by the special IP address they were addressed to.
+ Thus, the services that ultimately receive them respond according to the
+ specified destination. For example, an HTTP service could route packets
+ addressed to 127.0.0.99:80 and 127.0.0.100:80 to different Web servers, or
+ to a single server that returns different web pages. To simplify such
+ testing, the hosts file may be configured to provide appropriate names for
+ each address.
+
+ Packets received on a non-loopback interface with a loopback source or
+ destination address must be dropped. Such packets are sometimes referred
+ to as Martian packets.[6] As with any other bogus packets, they may be
+ malicious and any problems they might cause can be avoided by applying
+ bogon filtering.
+
+
+ Special cases
+
+
+ Reti di Calcolatori
+ localhost
+ Loopback
+ Name resolution
+ IETF standards
+ Packet processing
+ special cases
+ Reti di Calcolatori
+ localhost
+ Loopback
+ Name resolution
+ IETF standards
+ Packet processing
+ special cases
+ Reti di Calcolatori
+ localhost
+ Loopback
+ Name resolution
+ IETF standards
+ Packet processing
+ special cases
+
+
+
+
+
\ No newline at end of file
diff --git a/TPSI/costanzo_francesco/html/esercizio_html_01/pagina.html b/TPSI/costanzo_francesco/html/esercizio_html_01/pagina.html
new file mode 100644
index 00000000..388ae054
--- /dev/null
+++ b/TPSI/costanzo_francesco/html/esercizio_html_01/pagina.html
@@ -0,0 +1,25 @@
+
+
+
+
+
+
+
+ (0,0)
+ (0,1)
+ (0,2)
+ (0,3)
+ (0,4)
+ (0,5)
+ (0,6)
+ (0,7)
+
+
+ (1,0)
+ (1,1)
+ (1,2)
+ (1,3)
+ (1,4)
+ (1,5)
+ (1,6)
+ (1,7)
+
+
+ (2,0)
+ (2,1)
+ (2,2)
+ (2,3)
+ (2,4)
+ (2,5)
+ (2,6)
+ (2,7)
+
+
+ (3,0)
+ (3,1)
+ (3,2)
+ (3,3)
+ (3,4)
+ (3,5)
+ (3,6)
+ (3,7)
+
+
+ (4,0)
+ (4,1)
+ (4,2)
+ (4,3)
+ (4,4)
+ (4,5)
+ (4,6)
+ (4,7)
+
+
+ (5,0)
+ (5,1)
+ (5,2)
+ (5,3)
+ (5,4)
+ (5,5)
+ (5,6)
+ (5,7)
+
+
+ (6,0)
+ (6,1)
+ (6,2)
+ (6,3)
+ (6,4)
+ (6,5)
+ (6,6)
+ (6,7)
+
+
+
+ (7,0)
+ (7,1)
+ (7,2)
+ (7,3)
+ (7,4)
+ (7,5)
+ (7,6)
+ (7,7)
+ Titolo della pagina
+
+
diff --git a/TPSI/costanzo_francesco/html/esercizio_html_02/costanzo_esercizio_html_02.html b/TPSI/costanzo_francesco/html/esercizio_html_02/costanzo_esercizio_html_02.html
new file mode 100644
index 00000000..77a573f0
--- /dev/null
+++ b/TPSI/costanzo_francesco/html/esercizio_html_02/costanzo_esercizio_html_02.html
@@ -0,0 +1,143 @@
+
+
+
+
+
+ Localhost
+ Loopback
+
+ 127.0.0.1 localhost
+ ::1 localhost
+ 127.0.0.1 localhost
+ ::1 localhost
+
+ The name may also be resolved by Domain Name System (DNS) servers, but
+ queries for this name should be resolved locally, and should not be
+ forwarded to remote name servers.
+
+ In addition to the mapping of localhost to the loopback addresses
+ (127.0.0.1 and ::1), localhost may also be mapped to other IPv4 (loopback)
+ addresses and it is also possible to assign other, or additional, names to
+ any loopback address. The mapping of localhost to addresses other than the
+ designated loopback address range in the hosts file or in DNS is not
+ guaranteed to have the desired effect, as applications may map the name
+ internally.
+
+ In the Domain Name System, the name localhost is reserved as a top-level
+ domain name, originally set aside to avoid confusion with the hostname
+ used for loopback purposes.[3] IETF standards prohibit domain name
+ registrars from assigning the name localhost.
+ IETF standards
+
+
+
+
+ An IPv4 or IPv6 address query for the name localhost must always resolve
+ to the respective loopback address, which is specified in a separate
+ standard. Applications may resolve the name to a loopback address
+ themselves, or pass it to the local name resolver mechanisms. When a name
+ resolver receives an address (A or AAAA) query for localhost, it should
+ return the appropriate loopback addresses, and negative responses for any
+ other requested record types. Queries for localhost should not be sent to
+ caching name servers. To avoid burdening the Domain Name System root
+ servers with traffic, caching name servers should never request name
+ server records for localhost, or forward resolution to authoritative name
+ servers. DNS registrars are precluded from delegating domain names in the
+ top-level domain localhost. When authoritative name servers receive
+ queries for 'localhost' in spite of the provisions mentioned resolve them
+ appropriately. The IPv4 loopback addresses are reserved within the IPv4
+ address space by the IETF "Special Use IPv4 Addresses" standard (RFC
+ 5735).[5] The reservation can be traced back to the November 1986
+ "Assigned Numbers" standard (RFC 990).
+
+
+ In contrast, the IETF "IP Version 6 Addressing Architecture" standard (RFC
+ 4291) reserves the single IPv6 loopback address ::1 within the IPv6
+ address space. The standard precludes the assignment of that address to
+ any physical interface, as well as its use as the source or destination
+ address in any packet sent to remote hosts. Any such packet that is
+ erroneously transmitted is not supposed to be routed, and should be
+ dropped by all routers or hosts that receive it.
+ Packet processing
+
+ Looped-back packets are distinguished from any other packets traversing
+ the TCP/IP stack only by the special IP address they were addressed to.
+ Thus, the services that ultimately receive them respond according to the
+ specified destination. For example, an HTTP service could route packets
+ addressed to 127.0.0.99:80 and 127.0.0.100:80 to different Web servers, or
+ to a single server that returns different web pages. To simplify such
+ testing, the hosts file may be configured to provide appropriate names for
+ each address.
+
+ Packets received on a non-loopback interface with a loopback source or
+ destination address must be dropped. Such packets are sometimes referred
+ to as Martian packets.[6] As with any other bogus packets, they may be
+ malicious and any problems they might cause can be avoided by applying
+ bogon filtering.
+ Special cases
+
+
+ One notable exception to the use of the 127.0.0.0/8 addresses is their use
+ in Multiprotocol Label Switching (MPLS) traceroute error detection, in
+ which their property of not being routable provides a convenient means to
+ avoid delivery of faulty packets to end users.
+ Localhost
+ Loopback
+
+ 127.0.0.1 localhost
+ ::1 localhost
+ 127.0.0.1 localhost
+ ::1 localhost
+
+ The name may also be resolved by Domain Name System (DNS) servers, but
+ queries for this name should be resolved locally, and should not be
+ forwarded to remote name servers.
+
+ In addition to the mapping of localhost to the loopback addresses
+ (127.0.0.1 and ::1), localhost may also be mapped to other IPv4 (loopback)
+ addresses and it is also possible to assign other, or additional, names to
+ any loopback address. The mapping of localhost to addresses other than the
+ designated loopback address range in the hosts file or in DNS is not
+ guaranteed to have the desired effect, as applications may map the name
+ internally.
+
+ In the Domain Name
+ System, the name localhost is reserved as a top-level domain name, originally
+ set aside to avoid confusion with the hostname used for loopback
+ purposes.[3] IETF standards prohibit domain name registrars from assigning
+ the name localhost.
+ IETF standards
+
+
+
+
+ An IPv4 or IPv6 address query for the name localhost must always resolve
+ to the respective loopback address, which is specified in a separate
+ standard. Applications may resolve the name to a loopback address
+ themselves, or pass it to the local name resolver mechanisms. When a name
+ resolver receives an address (A or AAAA) query for localhost, it should
+ return the appropriate loopback addresses, and negative responses for any
+ other requested record types. Queries for localhost should not be sent to
+ caching name servers. To avoid burdening the Domain Name System root
+ servers with traffic, caching name servers should never request name
+ server records for localhost, or forward resolution to authoritative name
+ servers. DNS registrars are precluded from delegating domain names in the
+ top-level domain localhost. When
+ name servers receive queries for
+ 'localhost' in spite of the provisions mentioned resolve them
+ appropriately. The IPv4 loopback addresses are reserved within the IPv4
+ address space by the IETF "Special Use IPv4 Addresses" standard (RFC
+ 5735).[5] The reservation can be traced back to the November 1986
+ "Assigned Numbers" standard (RFC 990).
+
+
+ In contrast, the
+ IETF
+ "IP Version 6 Addressing Architecture" standard (RFC 4291) reserves the
+ single IPv6 loopback address ::1 within the IPv6 address space. The
+ standard precludes the assignment of that address to any physical
+ interface, as well as its use as the source or destination address in any
+ packet sent to remote hosts. Any such packet that is erroneously
+ transmitted is not supposed to be routed, and should be dropped by all
+ routers or hosts that receive it.
+ Packet processing
+
+ Looped-back packets are distinguished from any other packets traversing
+ the TCP/IP stack only by the special IP address they were addressed to.
+ Thus, the services that ultimately receive them respond according to the
+ specified destination. For example, an HTTP service could route packets
+ addressed to 127.0.0.99:80 and 127.0.0.100:80 to different Web servers, or
+ to a single server that returns different web pages. To simplify such
+ testing, the hosts file may be configured to provide appropriate names for
+ each address.
+
+ Packets received on a non-loopback interface with a loopback source or
+ destination address must be dropped. Such packets are sometimes referred
+ to as Martian packets.[6] As with any other bogus packets, they may be
+ malicious and any problems they might cause can be avoided by applying
+ bogon filtering.
+ Special cases
+
+
+ One notable exception to the use of the 127.0.0.0/8 addresses is their use
+ in Multiprotocol Label Switching (MPLS) traceroute error detection, in
+ which their property of not being routable provides a convenient means to
+ avoid delivery of faulty packets to end users.
+ Localhost
+ Loopback
+
+ 127.0.0.1 localhost
+ ::1 localhost
+ 127.0.0.1 localhost
+ ::1 localhost
+
+
+
+ The name may also be resolved by Domain Name System (DNS) servers, but
+ queries for this name should be resolved locally, and should not be
+ forwarded to remote name servers.
+
+ In addition to the mapping of localhost to the loopback addresses
+ (127.0.0.1 and ::1), localhost may also be mapped to other IPv4 (loopback)
+ addresses and it is also possible to assign other, or additional, names to
+ any loopback address. The mapping of localhost to addresses other than the
+ designated loopback address range in the hosts file or in DNS is not
+ guaranteed to have the desired effect, as applications may map the name
+ internally.
+
+ In the Domain Name
+ System, the name localhost is reserved as a top-level domain name, originally
+ set aside to avoid confusion with the hostname used for loopback
+ purposes.[3] IETF standards prohibit domain name registrars from assigning
+ the name localhost.
+ IETF standards
+
+
+
+
+
+ An IPv4 or IPv6 address query for the name localhost must always resolve
+ to the respective loopback address, which is specified in a separate
+ standard. Applications may resolve the name to a loopback address
+ themselves, or pass it to the local name resolver mechanisms. When a name
+ resolver receives an address (A or AAAA) query for localhost, it should
+ return the appropriate loopback addresses, and negative responses for any
+ other requested record types. Queries for localhost should not be sent to
+ caching name servers. To avoid burdening the Domain Name System root
+ servers with traffic, caching name servers should never request name
+ server records for localhost, or forward resolution to authoritative name
+ servers. DNS registrars are precluded from delegating domain names in the
+ top-level domain localhost. When
+ name servers receive queries for
+ 'localhost' in spite of the provisions mentioned resolve them
+ appropriately. The IPv4 loopback addresses are reserved within the IPv4
+ address space by the IETF "Special Use IPv4 Addresses" standard (RFC
+ 5735).[5] The reservation can be traced back to the November 1986
+ "Assigned Numbers" standard (RFC 990).
+
+
+ In contrast, the
+ IETF
+ "IP Version 6 Addressing Architecture" standard (RFC 4291) reserves the
+ single IPv6 loopback address ::1 within the IPv6 address space. The
+ standard precludes the assignment of that address to any physical
+ interface, as well as its use as the source or destination address in any
+ packet sent to remote hosts. Any such packet that is erroneously
+ transmitted is not supposed to be routed, and should be dropped by all
+ routers or hosts that receive it.
+ Packet processing
+
+
+
+
+ Looped-back packets are distinguished from any other packets traversing
+ the TCP/IP stack only by the special IP address they were addressed to.
+ Thus, the services that ultimately receive them respond according to the
+ specified destination. For example, an HTTP service could route packets
+ addressed to 127.0.0.99:80 and 127.0.0.100:80 to different Web servers, or
+ to a single server that returns different web pages. To simplify such
+ testing, the hosts file may be configured to provide appropriate names for
+ each address.
+
+ Packets received on a non-loopback interface with a loopback source or
+ destination address must be dropped. Such packets are sometimes referred
+ to as Martian packets.[6] As with any other bogus packets, they may be
+ malicious and any problems they might cause can be avoided by applying
+ bogon filtering.
+ Special cases
+
+
+ One notable exception to the use of the 127.0.0.0/8 addresses is their use
+ in Multiprotocol Label Switching (MPLS) traceroute error detection, in
+ which their property of not being routable provides a convenient means to
+ avoid delivery of faulty packets to end users.
+ Localhost
+
+
+ “I computer sono incredibilmente veloci, accurati e stupidi. Gli uomini sono incredibilmente lenti, inaccurati e intelligenti. L'insieme dei due costituisce una forza incalcolabile.”
Albert Einstain
+ Loopback
+
+ 127.0.0.1 localhost
+ ::1 localhost
+ 127.0.0.1 localhost
+ ::1 localhost
+
+
+
+ The name may also be resolved by Domain Name System (DNS) servers, but
+ queries for this name should be resolved locally, and should not be
+ forwarded to remote name servers.
+
+ In addition to the mapping of localhost to the loopback addresses
+ (127.0.0.1 and ::1), localhost may also be mapped to other IPv4 (loopback)
+ addresses and it is also possible to assign other, or additional, names to
+ any loopback address. The mapping of localhost to addresses other than the
+ designated loopback address range in the hosts file or in DNS is not
+ guaranteed to have the desired effect, as applications may map the name
+ internally.
+
+ In the Domain Name
+ System, the name localhost is reserved as a top-level domain name, originally
+ set aside to avoid confusion with the hostname used for loopback
+ purposes.[3] IETF standards prohibit domain name registrars from assigning
+ the name localhost.
+ IETF standards
+
+
+
+
+
+
+ An IPv4 or IPv6 address query for the name localhost must always resolve
+ to the respective loopback address, which is specified in a separate
+ standard. Applications may resolve the name to a loopback address
+ themselves, or pass it to the local name resolver mechanisms. When a name
+ resolver receives an address (A or AAAA) query for localhost, it should
+ return the appropriate loopback addresses, and negative responses for any
+ other requested record types. Queries for localhost should not be sent to
+ caching name servers. To avoid burdening the Domain Name System root
+ servers with traffic, caching name servers should never request name
+ server records for localhost, or forward resolution to authoritative name
+ servers. DNS registrars are precluded from delegating domain names in the
+ top-level domain localhost. When
+ name servers receive queries for
+ 'localhost' in spite of the provisions mentioned resolve them
+ appropriately. The IPv4 loopback addresses are reserved within the IPv4
+ address space by the IETF
"Special Use IPv4 Addresses" standard (RFC
+ 5735).[5] The reservation can be traced back to the November 1986
+ "Assigned Numbers" standard (RFC 990).
+
+ “Chiunque consideri i metodi aritmetici metodi di produrre numeri casuali è, naturalmente, in uno stato di peccato.”
+
+
+
+ In contrast, the
+ IETF
+ "IP Version 6 Addressing Architecture" standard (RFC 4291) reserves the
+ single IPv6 loopback address ::1 within the IPv6 address space. The
+ standard precludes the assignment of that address to any physical
+ interface, as well as its use as the source or destination address in any
+ packet sent to remote hosts. Any such packet that is erroneously
+ transmitted is not supposed to be routed, and should be dropped by all
+ routers or hosts that receive it.
+
+
+
+ The processing of any packet sent to a loopback address, is implemented in
+ the link layer of the TCP/IP stack. Such packets are never passed to any
+ network interface controller (NIC) or hardware device driver and must not
+ appear outside of a computing system, or be routed by any router. This
+ permits software testing and local services in the absence of any hardware
+ network interfaces.
+ Looped-back packets are distinguished from any other packets traversing
+ the TCP/IP stack only by the special IP address they were addressed to.
+ Thus, the services that ultimately receive them respond according to the
+ specified destination. For example, an HTTP service could route packets
+ addressed to 127.0.0.99:80
and 127.0.0.100:80 to different Web servers, or
+ to a single server that returns different web pages. To simplify such
+ testing, the hosts file may be configured to provide appropriate names for
+ each address.
+
+ Packets received on a non-loopback interface with a loopback source or
+ destination address must be dropped. Such packets are sometimes referred
+ to as Martian packets.[6] As with any other bogus packets, they may be
+ malicious and any problems they might cause can be avoided by applying
+ bogon filtering.
+
+ The releases of the
+ MySQL database
+ differentiate between the use of the hostname localhost and the use of the
+ addresses 127.0.0.1 and ::1.[7] When
qusing localhost as the destination in
+ a client connector interface of an application, the MySQL application
+ programming interface connects to the database using a Unix domain socket,
+ while a TCP connection via the loopback interface requires the direct use
+ of the explicit address.
+ One notable exception to the use of the 127.0.0.0/8 addresses is their use
+ in Multiprotocol Label Switching
(MPLS) traceroute error detection, in
+ which their property of not being routable provides a convenient means to
+ avoid delivery of faulty packets to end users.
+
+ The local loopback mechanism may be used to run a network service on a
+ host without requiring a physical network interface, or without making the
+ service accessible from the networks the computer may be connected to. For
+ example, a locally installed website may be accessed from a Web browser by
+ the URL http://localhost to display its home page. The name localhost
+ normally resolves to the IPv4 loopback address 127.0.0.1, and to the
+ IPv6
+ loopback address ::1.
+
+ “I computer sono incredibilmente veloci, accurati e stupidi. Gli uomini sono incredibilmente lenti,
+ inaccurati e intelligenti. L'insieme dei due costituisce una forza incalcolabile.”
Albert Einstain
+
+ IPv4
+ network
+ standards reserve the entire address block
+ 127.0.0.0/8 (more than 16 million addresses) for loopback purposes.[2]
+ That means any packet sent to any of those addresses is looped back. The
+ address 127.0.0.1 is the standard address for IPv4
+ loopback
+ traffic; the rest are not supported by all operating systems. However,
+ they can be used to set up multiple server applications on the host, all
+ listening on the same port number. The IPv6 standard assigns only a single
+ address for loopback: ::1. The resolution of the name localhost to one or
+ more IP addresses is normally configured by the following lines in the
+ operating system's hosts file:IPv4 network standards reserve the entire
+ address block 127.0.0.0/8 (more than 16 million addresses) for loopback
+ purposes.[2] That means any packet sent
+ to any of those addresses is looped back. The address 127.0.0.1 is the
+ standard address for IPv4 loopback traffic; the rest are not supported by
+ all operating systems. However, they can be used to set up multiple server
+ applications on the host, all listening on the same port number. The IPv6
+ standard assigns only a single address for loopback: ::1. The resolution
+ of the name localhost to one or more IP addresses is normally configured
+ by the following lines in the operating system's hosts file:
+ 127.0.0.1 localhost
+ ::1 localhost
+ 127.0.0.1 localhost
+ ::1 localhost
+
+
+
+ The name may also be resolved by Domain Name System (DNS) servers, but
+ queries for this name should be resolved locally, and should not be
+ forwarded to remote name servers.
+
+ In addition to the mapping of localhost to the loopback addresses
+ (127.0.0.1 and ::1), localhost may also be mapped to other IPv4 (loopback)
+ addresses and it is also possible to assign other, or additional, names to
+ any loopback address. The mapping of localhost to addresses other than the
+ designated loopback address range in the hosts file or in DNS is not
+ guaranteed to have the desired effect, as applications may map the name
+ internally.
+
+ In the Domain Name
+ System, the name localhost is reserved as a top-level domain name, originally
+ set aside to avoid confusion with the hostname used for loopback
+ purposes.[3] IETF standards prohibit domain name registrars from assigning
+ the name localhost.
+
+
+
+ The name localhost is reserved for loopback purposes by RFC 6761
+ (Special-Use Domain Names),[4] which achieved the Proposed Standard
+ maturity level in February 2013. The standard sets forth a number of
+ special considerations governing the use of the name in the Domain Name
+ System:
+
+
+
+ An IPv4 or IPv6 address query for the name localhost must always resolve
+ to the respective loopback address, which is specified in a separate
+ standard. Applications may resolve the name to a loopback address
+ themselves, or pass it to the local name resolver mechanisms. When a name
+ resolver receives an address (A or AAAA) query for localhost, it should
+ return the appropriate loopback addresses, and negative responses for any
+ other requested record types. Queries for localhost should not be sent to
+ caching name servers. To avoid burdening the Domain Name System root
+ servers with traffic, caching name servers should never request name
+ server records for localhost, or forward resolution to authoritative name
+ servers. DNS registrars are precluded from delegating domain names in the
+ top-level domain localhost. When
+ name servers receive queries for
+ 'localhost' in spite of the provisions mentioned resolve them
+ appropriately. The IPv4 loopback addresses are reserved within the IPv4
+ address space by the IETF
"Special Use IPv4 Addresses" standard (RFC
+ 5735).[5] The reservation can be traced back to the November 1986
+ "Assigned Numbers" standard (RFC 990).
+
+ “Chiunque consideri i metodi aritmetici metodi di produrre numeri casuali è, naturalmente, in uno stato di peccato.” ++
sudo pacman -S IETF
+ Quest'ultimo è un comando inutile che non funziona+ +
+
+
+ The processing of any packet sent to a loopback address, is implemented in
+ the link layer of the TCP/IP stack. Such packets are never passed to any
+ network interface controller (NIC) or hardware device driver and must not
+ appear outside of a computing system, or be routed by any router. This
+ permits software testing and local services in the absence of any hardware
+ network interfaces.
+ Looped-back packets are distinguished from any other packets traversing
+ the TCP/IP stack only by the special IP address they were addressed to.
+ Thus, the services that ultimately receive them respond according to the
+ specified destination. For example, an HTTP service could route packets
+ addressed to 127.0.0.99:80
and 127.0.0.100:80 to different Web servers, or
+ to a single server that returns different web pages. To simplify such
+ testing, the hosts file may be configured to provide appropriate names for
+ each address.
+
+ Packets received on a non-loopback interface with a loopback source or
+ destination address must be dropped. Such packets are sometimes referred
+ to as Martian packets.[6] As with any other bogus packets, they may be
+ malicious and any problems they might cause can be avoided by applying
+ bogon filtering.
+
+ The releases of the
+ MySQL database
+ differentiate between the use of the hostname localhost and the use of the
+ addresses 127.0.0.1 and ::1.[7] When
qusing localhost as the destination in
+ a client connector interface of an application, the MySQL application
+ programming interface connects to the database using a Unix domain socket,
+ while a TCP connection via the loopback interface requires the direct use
+ of the explicit address.
+ One notable exception to the use of the 127.0.0.0/8 addresses is their use
+ in Multiprotocol Label Switching
(MPLS) traceroute error detection, in
+ which their property of not being routable provides a convenient means to
+ avoid delivery of faulty packets to end users.
+
+ The local loopback mechanism may be used to run a network service on a
+ host without requiring a physical network interface, or without making the
+ service accessible from the networks the computer may be connected to. For
+ example, a locally installed website may be accessed from a Web browser by
+ the URL http://localhost to display its home page. The name localhost
+ normally resolves to the IPv4 loopback address 127.0.0.1, and to the
+ IPv6
+ loopback address ::1.
+
+ “I computer sono incredibilmente veloci, accurati e stupidi. Gli uomini sono incredibilmente lenti,
+ inaccurati e intelligenti. L'insieme dei due costituisce una forza incalcolabile.”
Albert Einstain
+
+ IPv4
+ network
+ standards reserve the entire address block
+ 127.0.0.0/8 (more than 16 million addresses) for loopback purposes.[2]
+ That means any packet sent to any of those addresses is looped back. The
+ address 127.0.0.1 is the standard address for IPv4
+ loopback
+ traffic; the rest are not supported by all operating systems. However,
+ they can be used to set up multiple server applications on the host, all
+ listening on the same port number. The IPv6 standard assigns only a single
+ address for loopback: ::1. The resolution of the name localhost to one or
+ more IP addresses is normally configured by the following lines in the
+ operating system's hosts file:IPv4 network standards reserve the entire
+ address block 127.0.0.0/8 (more than 16 million addresses) for loopback
+ purposes.[2] That means any packet sent
+ to any of those addresses is looped back. The address 127.0.0.1 is the
+ standard address for IPv4 loopback traffic; the rest are not supported by
+ all operating systems. However, they can be used to set up multiple server
+ applications on the host, all listening on the same port number. The IPv6
+ standard assigns only a single address for loopback: ::1. The resolution
+ of the name localhost to one or more IP addresses is normally configured
+ by the following lines in the operating system's hosts file:
+ 127.0.0.1 localhost
+ ::1 localhost
+ 127.0.0.1 localhost
+ ::1 localhost
+ totale
+
+
+
+
+ The name localhost is reserved for loopback purposes by RFC 6761
+ (Special-Use Domain Names),[4] which achieved the Proposed Standard
+ maturity level in February 2013. The standard sets forth a number of
+ special considerations governing the use of the name in the Domain Name
+ System:
+
+
+
+ An IPv4 or IPv6 address query for the name localhost must always resolve
+ to the respective loopback address, which is specified in a separate
+ standard. Applications may resolve the name to a loopback address
+ themselves, or pass it to the local name resolver mechanisms. When a name
+ resolver receives an address (A or AAAA) query for localhost, it should
+ return the appropriate loopback addresses, and negative responses for any
+ other requested record types. Queries for localhost should not be sent to
+ caching name servers. To avoid burdening the Domain Name System root
+ servers with traffic, caching name servers should never request name
+ server records for localhost, or forward resolution to authoritative name
+ servers. DNS registrars are precluded from delegating domain names in the
+ top-level domain localhost. When
+ name servers receive queries for
+ 'localhost' in spite of the provisions mentioned resolve them
+ appropriately. The IPv4 loopback addresses are reserved within the IPv4
+ address space by the IETF
"Special Use IPv4 Addresses" standard (RFC
+ 5735).[5] The reservation can be traced back to the November 1986
+ "Assigned Numbers" standard (RFC 990).
+
+ “Chiunque consideri i metodi aritmetici metodi di produrre numeri casuali è, naturalmente, in uno stato di peccato.” ++
sudo pacman -S IETF
+ Quest'ultimo è un comando inutile che non funziona+
+
+
+ The processing of any packet sent to a loopback address, is implemented in
+ the link layer of the TCP/IP stack. Such packets are never passed to any
+ network interface controller (NIC) or hardware device driver and must not
+ appear outside of a computing system, or be routed by any router. This
+ permits software testing and local services in the absence of any hardware
+ network interfaces.
+
+ Looped-back packets are distinguished from any other packets traversing
+ the TCP/IP stack only by the special IP address they were addressed to.
+ Thus, the services that ultimately receive them respond according to the
+ specified destination. For example, an HTTP service could route packets
+ addressed to 127.0.0.99:80
and 127.0.0.100:80 to different Web servers, or
+ to a single server that returns different web pages. To simplify such
+ testing, the hosts file may be configured to provide appropriate names for
+ each address.
+
+ Packets received on a non-loopback interface with a loopback source or
+ destination address must be dropped. Such packets are sometimes referred
+ to as Martian packets.[6] As with any other bogus packets, they may be
+ malicious and any problems they might cause can be avoided by applying
+ bogon filtering.
+
+ The releases of the
+ MySQL database
+ differentiate between the use of the hostname localhost and the use of the
+ addresses 127.0.0.1 and ::1.[7] When
qusing localhost as the destination in
+ a client connector interface of an application, the MySQL application
+ programming interface connects to the database using a Unix domain socket,
+ while a TCP connection via the loopback interface requires the direct use
+ of the explicit address.
+
+ One notable exception to the use of the 127.0.0.0/8 addresses is their use
+ in Multiprotocol Label Switching
(MPLS) traceroute error detection, in
+ which their property of not being routable provides a convenient means to
+ avoid delivery of faulty packets to end users.
+
+ The local loopback mechanism may be used to run a network service on a + host without requiring a physical network interface, or without making the + service accessible from the networks the computer may be connected to. For + example, a locally installed website may be accessed from a Web browser by + the URL http://localhost to display its home page. The name localhost + normally resolves to the IPv4 loopback address 127.0.0.1, and to the + IPv6 +
+ IPv4
+ network
+ standards reserve the entire address block
+ 127.0.0.0/8 (more than 16 million addresses) for loopback purposes.[2]
+ That means any packet sent to any of those addresses is looped back. The
+ address 127.0.0.1 is the standard address for IPv4
+ loopback
+ traffic; the rest are not supported by all operating systems. However,
+ they can be used to set up multiple server applications on the host, all
+ listening on the same port number. The IPv6 standard assigns only a single
+ address for loopback: ::1. The resolution of the name localhost to one or
+ more IP addresses is normally configured by the following lines in the
+ operating system's hosts file:IPv4 network standards reserve the entire
+ address block 127.0.0.0/8 (more than 16 million addresses) for loopback
+ purposes.[2] That means any packet sent
+ to any of those addresses is looped back. The address 127.0.0.1 is the
+ standard address for IPv4 loopback traffic; the rest are not supported by
+ all operating systems. However, they can be used to set up multiple server
+ applications on the host, all listening on the same port number. The IPv6
+ standard assigns only a single address for loopback: ::1. The resolution
+ of the name localhost to one or more IP addresses is normally configured
+ by the following lines in the operating system's hosts file:
+
+
+
+ The name localhost is reserved for loopback purposes by RFC 6761
+ (Special-Use Domain Names),[4] which achieved the Proposed Standard
+ maturity level in February 2013. The standard sets forth a number of
+ special considerations governing the use of the name in the Domain Name
+ System:
+
+
+
+ An IPv4 or IPv6 address query for the name localhost must always resolve
+ to the respective loopback address, which is specified in a separate
+ standard. Applications may resolve the name to a loopback address
+ themselves, or pass it to the local name resolver mechanisms. When a name
+ resolver receives an address (A or AAAA) query for localhost, it should
+ return the appropriate loopback addresses, and negative responses for any
+ other requested record types. Queries for localhost should not be sent to
+ caching name servers. To avoid burdening the Domain Name System root
+ servers with traffic, caching name servers should never request name
+ server records for localhost, or forward resolution to authoritative name
+ servers. DNS registrars are precluded from delegating domain names in the
+ top-level domain localhost. When
+ name servers receive queries for
+ 'localhost' in spite of the provisions mentioned resolve them
+ appropriately. The IPv4 loopback addresses are reserved within the IPv4
+ address space by the IETF©
"Special Use IPv4 Addresses" standard (RFC
+ 5735).[5] The reservation can be traced back to the November 1986
+ "Assigned Numbers" standard (RFC 990).
+
+ “Chiunque consideri i metodi aritmetici metodi di produrre numeri casuali è, naturalmente, in uno stato di peccato.” ++
sudo pacman -S IETF©
+ Quest'ultimo è un comando inutile che non funziona+
+
+
+ The processing of any packet sent to a loopback address, is implemented in
+ the link layer of the TCP/IP stack. Such packets are never passed to any
+ network interface controller (NIC) or hardware device driver and must not
+ appear outside of a computing system, or be routed by any router. This
+ permits software testing and local services in the absence of any hardware
+ network interfaces.
+
+ Looped-back packets are distinguished from any other packets traversing
+ the TCP/IP stack only by the special IP address they were addressed to.
+ Thus, the services that ultimately receive them respond according to the
+ specified destination. For example, an HTTP service could route packets
+ addressed to 127.0.0.99:80
and 127.0.0.100:80 to different Web servers, or
+ to a single server that returns different web pages. To simplify such
+ testing, the hosts file may be configured to provide appropriate names for
+ each address.
+
+ Packets received on a non-loopback interface with a loopback source or
+ destination address must be dropped. Such packets are sometimes referred
+ to as Martian packets.[6] As with any other bogus packets, they may be
+ malicious and any problems they might cause can be avoided by applying
+ bogon filtering.
+
+ The releases of the
+ MySQL database
+ differentiate between the use of the hostname localhost and the use of the
+ addresses 127.0.0.1 and ::1.[7] When
qusing localhost as the destination in
+ a client connector interface of an application, the MySQL application
+ programming interface connects to the database using a Unix domain socket,
+ while a TCP connection via the loopback interface requires the direct use
+ of the explicit address.
+
+ One notable exception to the use of the 127.0.0.0/8 addresses is their use
+ in Multiprotocol Label Switching
(MPLS) traceroute error detection, in
+ which their property of not being routable provides a convenient means to
+ avoid delivery of faulty packets to end users.
+
| Q.tà | +Descrizione | +Costo Unitario | +Totale | +
|---|---|---|---|
| 3 | +mouse | +15 € | +45 € | +
| 3 | +tastiera da 105 tasti | +20 € | +60 € | +1 | +stampante deskjet colori | +110 € | +110 € | + +
| 1 | +scanner A4 colori | +220 € | +220 € | +
| Totale Ordine | +435 € | +||
| Servizi ecosistemici | +Codice | + + +|
|---|---|---|
| Servizi di fornitura | +Coltivazioni | +F1 | +
| Foraggio, pascolo | +F2 | +|
| Specie cacciabili/pesci | +F3 | +|
| Materie prime (legno,fibre,...) | +F4 | +|
| Funghi, frutti di bosco, piante commestibili | +F5 | +|
| Servizi di regolazione | +Sequestro del carbonio | +R1 | +
| Regiolazione del clima locale/ purificazione dell'aria | +R2 | +|
| Regiolazione delle acqua (ricarica delle falde) | +R3 | +|
| Purificazione dell'acqua | +R4 | +|
| + Protezione dell'erosione e dissesti geologici (frane, instabilità, + versanti) + | +R5 | +|
| Protezione dai dissesti geologici (piene, inondazioni) | +R6 | +
| Quick | brown fox | jumps | +|
| over the | lazy | dog | and | +
| then | it | tall | +|
| prey to a hunter | +|||
+
+
|
+
|
+
|
+
+
|
+ ||||
|---|---|---|---|---|---|---|---|
| Yes | Yes | Yes | Yes |
| cella n.1 | + | ||
| cella n.3 | cella n.4 | +||
| Tabella | |||||
0t)6zDr$9iJZHOQS(jb+X!>p-R9E#2vbZTLG2PQ#3ZVT|uxRfn;d@*q;WRJCR< zylZp==TUB3shh^kwV<1Z>saJ-3M%L9h;oW~oEGw;H%sO%|VK#?)` z88FCaPgEsS=%-UJxMK~{$A)tp7f4Hy5_*`O>kmmAmzbFi3?zC{+$ndeJfZX@MD`&B z7dStWNvW;v@~-3GQBbH;oXpb$DL6u9QD^tQkooNf1_tbu1sei?84v^nrP{}}8a(qD zDa40sdG+ z~yh)pu_Df zPNhiG@>4@O8oj?|drYeE^kKuVbz z)w);EPQv<}XeS7aGo>6q)LGsE>8#-ATB5?DAsQ$BIm(aCDdzlwNg8s>t(Bqs+SP^S z{nCS)VDo+FY_2Q{c(4Td)9h2}m!6|X`Iryb4g=5zr(v!>Hk})&naty09we{AaCf{L zj0j3e&vyG`%!0eda{|l@Qs);bW?k$1K)xAdZ&1FK$Y(Dg@CUvQd+lwTA}+O)r-D16 zS)+E_C}kC*X_XHM+MEl&Ms6=GurPh)_B1J^d}j>gY4kEqsq|b=lXk_ibttbi4|AQa z4{5Fo2uvH}p&Cs8LYIs>qYgp+%)9u18 x#&;s_M7e=1%d;sS0 q2?Jp^xIAr6}EX%NR)&flmRu{p>1sr^|WT&6#o7#t@5ETcrK6s{zV+RGBz z-#fZi#Ie_vu%XvZf>dv0TH}634nh0Je7mFB9)ryH8}UinNvPOzu=5>RkCEg?k7Uha z7MI{O7Sq_UoQcrh7YM=ldRHzko>W(OMv$kca-6hsI?quVw6V}q3YOWq$_N1fF0uY1 z;0`?m-PIqPyKY3RB`2LA!=XCfnYX5B@^^!y5j&}0{g3tUel*>)F?OSDMPQVW&!pdx zY0)BN7I{!HD|R*6C6?-Vud$uUF2&c{`xE%-q(i{`#d>+spClQvHJ_>~`W?K)W{y`* z2<_i|pB~9OSz {$2PW z_Et6QrkaO^!z({wQkj~iASveFsH+Jo-ej5w=I7K%FpJYgEOe}f9Wj+fbC+v-7>v5C z%ebi7$!{gqc4o=Xagi{SQ{~~XK!K*{bM0K}CH+H>K%T<6r489R)^xBvHhTeDC|isG zzX(BX=rs;;?XyXF4LdUZJkV@X;HJZMWGxwqFBm!k|D-fpXM~ro`v-*sy&`B4tswul zhTaScH#OtJ*E&0Inz5?;n3Ye=*J@tK>FRvvT|c8l6Vm>k_RO7EpG~lmZb?7A>()YT zFs}P) ph+&p3_65|j~2Qr z)fsfCSXZq=abuXe* Di1NwcO=esk_w2NdXass_ zHE4-Gw){|Xb^GXDh(YtV{W7C#n3nWQ%Ry@+4LeRgu#fA$g1q4?90gV?mDBatWq;8w z3w2pC#PFHVyqUaUgEi+?i{De0X(Tp^%$(vEay4aNWps{Gd&2GZzPN9p$*(kT) 7M&eZTJ8&W<{FUl->wDP;OZJdSsIRGNriMwGHBL`i>iEW3moy8I4<9Xp zAaBTboy=S{ZfKH91`s!(4xS=pK_}DLO7)n}Aq3J`bJTIJ0K %MeEB#!w#fF?Z4ObgtxVXAUA&nRJncsb_x(0j!+=Ev1af_v)FdW z=-zBY+>g~-S?*#0rU_7!373RT{uXmQb9y*`q)sexV?PWmF#I=A?TjuFgjh4WcyV!*Zay2SHL3 {O$l$=fc>6!;O;U;;` z^1h3#Gl 87pb{v#WgF^D7t;7u3xkaRb8oiokD}p_3E*5)#WMf zS }7FNYU zgbipEyLlBB37Wvar0~OvGUv6Z@2Xz|7r)%Vw{GbP?=m_mKRV2W-J$+5^ACZ*iDvos ztLrAFsNPJ?39t0;p$%7|x;HTr0oHf-)biZcoe^t1MRWI `|KO!U*F% znIn?kwE$-OZ-y~!3y-cMA6OzEz>Kv+v`NVq4{oa|I =djQJHnGd<%0k`Sr}vBCF5cZ@hfRVZ z7YiuKch3iuj*p-!DOL45%}*W|wTfEI1tqd{5}po-Q`7XEMk)VbaMqw @d&g}#u}x5(SslcuEj9@jr*z!=>;J>!3=%U<>ZG^p zW;t|aiy~8Bd3G1HJpH9@`_S|?_Gq0snWouD&M9+vIqsKg4n=KwL(+)9dn(ZX p$#Q;!h1Lc8XUPDp`UgzB`hed>S!;}luTtTCUERj>ByO+p z#BjH-KU$<@P)(L)z-~?Eh?p7h`UqH+6IU8> W!di@EMBI)Vw%5fo_!qghdy*GZyXkkA7cQF3nZ+Ze$+BCx+++|>B zBYYL=8&_KgTBEdG^!m~A$UDoKbw`4@mu@h}mA}&|nWh(vz}p pEzfr+3{3CzaS=j6rwGANDkX{(SU5Ncg{WpN{<>?DSG9 literal 0 HcmV?d00001 diff --git a/TPSI/costanzo_francesco/html/esercizio_html_10/immagini/google.jpeg b/TPSI/costanzo_francesco/html/esercizio_html_10/immagini/google.jpeg new file mode 100644 index 0000000000000000000000000000000000000000..361837d215abba267b10dfd2a815a7fb03c81b3a GIT binary patch literal 8222 zcmZvA1z3~s_xA>a5u${IASECO3?xRUNJ~hkAV`kxQPM~Z1f;vAyFnC5>6Y#Rqok$( z)9?TL{(kR!z0a oP>g!g^q%fiHd@Ro{OI88QXIX4hmWx0Uikd zGYAI<5DyRUKEZt|LP9DC6CD$T4FchWKp<>v5Ki LLkt;%bb7yakBm4Kwp2? z?!E$uZ~!ZS6-*!z0D}mKNd&y>1UyCyh=B?GBkR8x5F3OA#>BuuKYc+60AgYQaY0~g zY#;~|&GCmDM8t)KO-wKO`mLisSS_ZC `yTG;XLAoONm>@pn5}Ig;fX*+-n~2)t&zRJ1H9dvkjz-D*2;)j{L!d-uh517CWZ z>>aY1P!v0%_E>i;Bb7vpU>s$wHS0P*e=Xz7(JjkVdX@#$6{IJh1c8763Bvy-!25Lg zamIXE3LE^KXMrjNGq1$P4i5q?Ls92<0OfKvtpZlA8R{?6Q{+;bMW>pV+TsKYw_vgU zN8dHI-zz )P`bn}SAst0g3Uh@px_7Z3R8 zN5=%D2d2j!wMjo~C2kh=oQZhAM=hIP-qw+qeO80z4P`}5KFQ3CGCQC@3#8ipQSZrc zjhwGMwu4+mDLQ39MB`Yv^oU D7W~~GMAS+YKCc9IdHsWf zQ%hmsN)7(kS^f{1+_-MXBH=~4)%Z{ZM=Z*^*sZ!^Mdj;^YnxAzgSAN@IvmqYk23|1 zi*sr}u5GP;DRxUYDqFnRED0zp(bMGV_n$I8@nPp~p5x#g56#rg!6#}}@KgBs|ELF$ zP{6eMcyuaFRY7v2=3}W`FI@1w6LzHgY%-p|aK+eEXVe&1_)2>g0*U?ZUJOGObK zxeMs>dxT2sqDVPLb-o^ydtm)AMXdbM-W>HX(umz|%Jk(wuK!mXHo=wj(UAs8KY8KM z5}NL) Vct3>+l09AQ}a6R{HK=1@>T7w_2bvBV}A;av4fb zzF20pC6G?$>oJ~z+r1}fM09kAFc@to_*y{nT=cVV74%I9eTA+)TAXH|1^kO$Ho={A zNVc&l`}R6mI+gPIN%Tsitw }n?=m81D$|hjAqR4w@*>M}`66L(OdM*;X znf@-Wwzz)I-NK0Cb3R20qc{E5M?VngGpGm%q?cd qY)qRQUV 0Z1}zsth+D-(oqsn(bIsc2pj zmRV|UGfX+A$bx=N^7&M7+O2uk#IK-nO}GkZ;={BCl{>N@^&^|Jn({7L_J5{+hg~%K z!Lf^rPd(+0+}7$xe?vp^EzU(N=30i3VQ={Z{u~>?FCGw2N5{wl%A#wu$91yl8>i~P z=a!_J_!&XskU&O`$IdQC&(6+4+|fDD6dcy5h>xG|#D2;!?@?2+SrFYyM- +f _ZJnn(Q>S6z7>8J|TO zr00~ImguFk>}a?diFieH%kR!~4;81%-hT2N)_n{axnE*O!GE3UFKeWnUmfYSRDHe= z;nmHQBzrjU{t+j0-#KQ^OcYJZ0!mY3%%f w4RdJOi+edX1H`6tI+uPvlY5#(vTo?0Uv&LPK@J&Yn>)&v_Vp!jK>Itel zr&V_?haan~^moQSugr4Fa2P+sOFP`s-w_C+#-}x_9O%Vd-9vIp1_vc8$G<-ood%YO zZ!)!w5vkX+CEX0w8|~|2U)YLoL=nv%aIrd6o43M%59b{~deMGbSt|(e2~0J_o`04S z#?&^e93jr&%HN~k)L48OI~70VOr)Lvd1Gbf*y?jpw45V_Z~w!|QTxmH^1j2QR_!@n zwA$c>_M#dCG7=OTm;cxXU&hKjC_Yb~Y1NO`e$l7u-j~7sUtd~mUT2|f;iO47%=h@m zscY6-e7=a4#5uX}4iJ5#GPV54#q1R}wbog}^5VHxSl?8IT5TOlxQ6L~0MzJ*U9Fr2 zCT`1{tLEZ2Y53%f3ZU|*Pea5I&>yDq{w}-J<0MjdZE p!KWEU;I`=Ld}zFkh@nmd#h<7 gQ&QX zp#WEwy{OYRuX0$jRcKey4bSkv1S_ToIu#JV@FT i6@W4=aPVET|zX5 zY|}(g>*_r%=Pt-+p04R!FL{|o4-C|#Mx4=#pQ9=Vbu$%j1oPTmL$;8&jW#|o=M$gA zMUM*bO9hM<07A0Jp20x Vj!u hYseY#qn+E(8fa)o6e?#Q vzAuAzg<$;^*prt z1t#;;QL!AImFU@+Z@CV$1|9%h5saj+zR$VT)>ZjR6A6l&B2hcB)!r_n+!Vp76b;0V z93t{fB9om@a!R9!+pM%cqg42;YkCCcqzL9L6q!101RTBEaV7^o3PjwyPq50|u%~ 6=v9e>IOmv8S6x_SS6Gg>kx zDc7SHVuHpB9gaL6ux_xg)@<~kHY!)=!tjkH-fU93%B8{75?hMS)|>R-WWlqaHW`Pl z5kfN!Jd%MYwMLf_2?z^#b>Jh2^%&}>Wde@|I&C8~hP`^WZ;y0}A)Bt3>hdt@W#m~| z)$U?TjiL6kX{m*|oP-O_4{oyssA6c%`75N&W+nm97v>DUw=wU0>DKnivV3~I4Nm (C_s%@*ppFd^Ne{lvhID8kr^x- z7BvidD-*^Zk>roGQVaQU&7)FC)Wc&JjV-7}f6{Qho$kE@3?>Q|{+d0})J!vCzNj+w zFS0@%vcaMuF91Ow{aAp&1F5Hxk-`~E_&XPnQUc{@5@kc!Owx|5URvU7S0fq0;}08f z-oo^S?E*1Q*Ld&Di6QHfHhHlIqzUKK=YByTB3CjV)e0d}Q?1n6oc%BGQwkMZL;`l{ zu8%ubL &&gdejo{2FdrIkSBaANpVll$N)IEy^FVQ3;&w z?|ah&fjAhL-Pwuc3+t^)h6bp1#chs&_Pv7J fl@U_oJY?!^5PX=yqrD%d2 zYrRU1e_7(~v-UA;)|r*@UCv1F*}=Hu(>E0kf_UF2Yd4dLYi#^%eV>yl-~UeAe#k;V zdqeKOIy%D^mXt{zo;K{nuV>N6teLNRu3smDk?mMfk%Z ?wv-t@?;DWo`^m=PJZXFtqe=I1 zy0jH^O7+U%!)*K&Ful!yLiQ})C!47rRx>?cI2Q5F$bLvxP`m5@QpAhpLrRfhRqeXB z%3Io5O_}7x-zLr1ap&wV)^`8~pEvfuT%m)B(yVz42f~X7++Q5S+{^gy0H0cCM$~6O z%`xkh86AKu!oOa7=G4$`IpFhzMfY_I&%omD_ycewM~80BrY312)715VCOCi)#27?J z&)kV 5q>foz%m5)t!y0(-E*)C82<$x3rerNIpl5E=pB~8{Bb>_hrBZ&;92@js z&76?^yA$auB`(@dFCB4q;~i=P*=>Wf m#9Pf|8~Rf05}MEC^uHFO?bLZ2Q@?U?7ib{BfFY9c2$6S1Ty`CTSoo?~ap%f) zjH|7dt=xRdFV_Zv&{ `yP$KW*<|xl72~_93AOake7e=W6{@qc#eViCAjbd)%`0j_Al3RYmW7(VOdj8 zT i9aX+hwh^!I%5X#kxmpkp-ufKilK?i{!ooUhuEaB zEko!+x1*`t)GD6rk7MTgP zD;(_ws>AJ3jSz;2n?ZNzSy@C)^!qCJ(EQPkx$~rwmqUL8fdoA+pDqUEng2e9Z{YBH z*$FkZw_f6P!Hp=KGO2GizA+(q?%{^L_?9S?s+Zh_QBII= o)W2Kpi>H#P8CYpwp7o^cp7A>BFlnQrdXP@@*^*G< z0cV-5dC~EP4-D#|gv~;lZ?%L*+@%?}f7~C_GUx97I}$o6DD*DBhlq+9`i20-jle5- z(v0i!cEkR*hC}fwf* V?HKgY;;}eVa>6{?=M+!*!<~|LbQ6g<~T8|%0F81b=&Ci z%0lY?4m9EuM}QxCPQik V2g x74A zs;jSMCa19jT|@v5gNHztmoj}qHM}50N9jhEnxrjM|3QbWe(^<*=1(MQ+y%Mvef7C^ z9EHRSfFB(_K*HcyO7s=5a*}u}IM8g$kYZkj!(zaZ!bZK!HnOr~%|I-9qsM `7?TYL>J(S9{}6QkH*UzI`0jeih-LAIM5Yqg!43wjl4OXt~hEU@FQR=lHK zq`PQ`yb)3@D8n-48Uhf@0bq>F7#;6e1cx(1WPMVZQ=2wlPDDai8N}>=K3{~gt(xLA zG@1WEH70AO AjVzu9%3 zv4fk2K512S$C32YKuU?!K94p|U1p_T#zgCu*;?&4x1Qy6bYW{m4gI)DV=8g^y#a zBn1Wg`VK_N)O#gfU%l$Rw6RskZrq(dd@EM8wYI$01e*??s?yJ6SzwKD^T`ZMgQ(@9 zOV2-DO%PCyPnVoiV>I S(x$_UWgFb zJ$P~W;}{LKRwt}5*+NB5@&+|OYL)ZD W|y_&J?vG#nitMJ z&*rVS fRP)G&fzP(=!`x}c70f18@m`X7;j4tGP=`}pUrvW3ER%T4()tuvu9LO1 zy`w`GT`wWl5)MY+$oIYG1-@nFBByph*pIyYWPN=Swes#W2fjzyai#b6DHj}u-W)ft zj2sx;CUh>GaP9eiXdlrLX8w?H6SKQ`b#&X$nkPi($HMscTrnL}ClVb$E-y%BjISV@ zsWF45QY+XKy5`!>%@zmm+3G{2+qu6s=Ty?+JP6By%_2p>(66<%%aUYtC$hC6aatCn zLn2Wq!3Clw``VuKBnQ-U5m~}oW&&-~j0)+o)acN+C2#JbvGM|tNB9>sl0dA;q@&2a zi5a9lkfA3=9X(!&moLq`*5&-+djG7L*&UNHbfBPSRYhL>(wDtcV99E(p-XbDl#aXF zkSIf|8;V)h<1E9xJrEp7VyIexylPP@rFpapV}-RB* akM-FpV(*O}O%X zO(HXk9jrvJ!>eV-0!LJFBp#v%nc#d8Y+39EVsHNVgkaq1&qd$)`zsm`1wTvoC0u&E zv?Z`3pxrjS!Q;wRQV&tw 7yt8I2eBD z^btE4^I4R{B~8@bJLF)&&68R7c9!zkNPoT2>lQCk(>GR2m%*fLP~s0iz^`y~%K9eH z(*wN33$r-Z >^Br$VAMMP&Im~uSnNXei;@Q3biw-fqNcaL*h!x{ZCayCzF>4? zh~Z~<#GzD|=W$(jnVGX)D-&5)GHG;Kp}qZG -U> zo-Fg(7z|Kx8b+@**c}GsLu^ZUq{sue#TqR(F9d_Cn$UA|MT0R(D>AxBNias8f?JB4 zMF$}|EdK>E`hY=oc^?5yi~#;PKbbM@cj)2Oz*aIjbGS#!uopQx^PEt)7-Vn~?o2u@ zv{dd_Qb>p7WViFr9luShLyVwnbifNaRRW|!A79PJ TMVE4|T=UhB2qUa}9ex zT8P4LpC9ro=CXC5Q^B7DMiWfQw2Klf%Q10x7BUk5Wg5|yV=BBJA#0g>27J6ZCvRo- zgldR1)d{m%#cnUO>JAXUBxU-|TH(Inr#j1_xZ1?3@;9#}|3Kxh8uIT3c2f)1ghL9f z?a6IL!2`cEh15w(Xu<_suf&=5gTCzy7bYljEQ&7r1b3;X%c;tv<;bG>D6yGNhM|(k zQ)QO>BHzkdUHd)HGCXY!3(oy5u3F#pG<`?d_gnwDp*g0s)B~$wn+uNN_fN{duxj!_ zKKv{()%aJPe{||DP7u`7Wusy+jCc$LXRD6EGt5Yttk`mb6I+D3PV5_QT87X1qGdhG z;Hr0k*!ueDC8cw5r%)p)sBrC5#G$ZraK(l4{m0T%*eL^LX-r@%HVV`O#=ip`%&Dm4 zv9_uj@>Hiq6#$1PCn>8;+T)E_?$^1jlcWO3Tc?3-7niay1S09Ve#VhUob#lUtF=Pj z{6?zq>_bzTl)}e}Ll(uIW@u;C=~y!lP+lqX3}O p+|C=V4eHU$qC3Wt^t2hU!D zvBEW;9Pt)gUOHX5!AWhhXZBp&Pkf^se;ei;1fOB9vXSI6#T1HQ>1 5V!t##n>YGCL)$*6_j*Jlx4ty3iPP7- z_OSZBbyZaeS*30n!DG@kR^Dxho};`gWo%mB!BbE6!oQK}KWO;R9U2$6!_uqfcr%Yn zAgfw=;hyMu0^|GpoY#(b084}BJAg}zQS$8TJHRVp@))zeo!oDf@q+<1P&5$!+Zi9+ G&HN8cXAXq` literal 0 HcmV?d00001 diff --git a/TPSI/costanzo_francesco/html/esercizio_html_10/immagini/opera.jpeg b/TPSI/costanzo_francesco/html/esercizio_html_10/immagini/opera.jpeg new file mode 100644 index 0000000000000000000000000000000000000000..608f5ab2e37be605b4880ddf1cb7fe825d36eb5f GIT binary patch literal 4551 zcmdT_i96Km`yLdfa~#`P!-*){$U0Ow)v<5c#xkhvh9NuIN+Ns3n2f IZm;_9+FmVBxxtLhEn2y>2XO9IkGqW74{QF~NJ8_bU zndQ`R_68?_nThEH>j`!?R<^$ijx#4ta&fb=om0GK&U45A0k61(l7(}?(`PS$=dZ^W z;NL1+x?~i#+z5PF*+02@3?h7N#4*D^DUJzPSee<5lWJVY7BMrko<70Ea`LZ|?+jcg zxqsk`9}_%%@wT58Ke>9HS7}W``Izeb(J K+_+8OaCuj1ecgw6wg=} z0SPs$2Elmc3>Av1sZ~cnl2gN5{16lpDl>2>v=$AH^`^C@L!=&$62jy6BKSk${=9m= zM}Uj;xo65ggYbgFy tSU!sa?i7)*y zJjN?Sn6@a5q}rO1c7IxBBxcwRRAqn1y8z>c_F!u;hZ$_C_$4N$OzH%ThAdFar7mPH z-OCR9_dzi$7TJ5~PIcre$lm&3<{HzB csPNn9|1QrI#kKA%9FFU)ttw&m^ z#E~lKI=eQ)9fjU!T~1bVEhQ|hMY#$sVw)LAc-$M?7E1&+V0l_gt3NYD6_fdz1A)^` z@yD(n0Y*5(%NsmX7P3eLM#fjg&a$Ol!7lDn*BAj8!wu}Vn`5g~cDn Z{B9gY1=uK2Pk-L`W`QTSA7T+`Z8A$mC6En &1FVlVbt|zvzw4j zJTH#;w9{4U0J3dFg>QoEvi-P#KDY>Er)M~UC!lT7vS(MXH>5M=dXT=wzl^x1vTl5s z?n@3b>hUd6JruKwis`8hf_|!8pb#mZj%O%t(cgl@^t5P8``a?JBQHnt AzS>` zDkr?a<|-y8(ld7=UE}6KSUA`XY%!0FyXHJ%(PIsI#mEmCE7S=KPsJ0w;s>@Ere*J_ zd6C*;jW^lMWLu0_Ys(#rA2p`L3o0?e7U;GXkMwCOv0?2KuLd)Q^Jaw7lV%iRR6*pG zX^V#jo}=4vy~v1`5y|?Ae_F+?h(Q@_0O?u1--yQ6+SXAe1ZrAeZI`mne#6tM$nqdi z>S6g7A% *8S2F_l{ET8uM1CzoUK`~c%(Hl-#($D3yReP9p4I!l zGdhKjrX9klNw+eufauqaSgS*Uj=1 t%y|21RQw%lE30WPk1j9I83n;sVz@gTu@3LllfzA`{ev%y z0SD+`u;ZqTmClyaPtxj?m@-137lOw)D_p`%(V2yx$XdmCvyv(ms!HG8wGb-U6D2dM zQ0SY}!e2%=CFYPzfRbbvqE_{q+3V`!S6JnQGxw;Fauc9myj|AopDz7L$PN$VNL9BC zGpt5vH`Z7(yxjKNB2Dbfk*af)9bY6rux~*^TU4|$l6RMB8~~`?GzxL6vaTk>GrmkN zb)GijpsA21mCu;&p<_M{p%)9O$39>yQ2u8wL_h<{w1!t1!yb@kmi_vDO?Wo<@DD7DHers^456ZL!w z>6#G}nf(aoIxt&3lY%Q=@~3I8?d;24w}|`M4A7}&IZAR}_t_}BspF<(!i-78JN1&q zKd;;>hQo%+=QMh{wJ(Csd+0l}a4KlBSMG==*-d2$P%NVeR||LFRaOa_|CTfFO$4dU zIM#>zZ26M06W`I9)@SzbtO_%T=US&TaDl3 zXaA5Cs;=IVLRvb=Tn`#=9Z*1XuYm8&$xu;FV QC2o{6x@R54NGaM5hV&xOFrs}alZ!X|vk zYcFd&zIiGn8H$xKKF&CZPnQg~I;3@N3=@;}PW{xzZf3{3r>RsrK5X^586j{4@N$gS z{)qgb0<@d(Otb4Oeczy*SmNu Tq^(QR(~Czh$?P w4ny2 z9}9y~TSxM`HXlvdt6%yl%nCJH6=ZX88GS*IW5;0nD_URu`Qq%d7P>J{6suu2rp+BY z ${GnpgHPp8ci?`yx5Kv)Ldlx&*24lMv+WBmU(O(k!R1oFq`~i8i{L^&N)Gqvq z9|RVtYtWXJZVEKl?#@u2^;dmty~Zb{mDeGAS2cOJ^l&WaCeOcPJpx>lBWh((B7ZLe zkMaX|UZxI(^?jCAA(D+H9qaWf+T<&{+VB6Zn3=0Ar?zDy7*gB>Q?`iwYSxB)FT4LT zQb&W5FS$+GNlWKZn+rBy6m}WAYQ=EosqXFlrS}clXCZoho`KB@Zx%wY>kXCEdbnni z&KtK{S9 ?d&&sbvp?YJ$Lb!|CkcIZ}+ehKG#l~iX?X+Lo}kf-T87iHOjPO;CzLo zDB?FttPA?@CID=Ra W?@#ZMB73vk3^>F8}kaN$(s)#Pneci~?SmuDnwBKD`!pR_E6J z&_YA&MO|KqQih>yj^7D)arb}()M9axJGNGr+8SgFq=mE~v@2^!@a2pZc;!G+u-D_e z0=V_)Wt$7>^n}7oTOWR!0^o#udRCD@o1U*bg*GzUr2*aOvJ)8aPRSWN} z-0 8mv*r$lW*jSjEbuGy;D>z?!C;u6%IV|sGB@BT=5Gyw)3 z hM(-@K8Ad+#o!KEX5W^ zgxedrx{jv;d%!^YitaFoYUU%2ZxE&Kek#P-yxfTlmunP#Zo7QbtmxhN>EdSo9EST& z8#GTwxIqG_xAwjv#-o23YA6@vl7egBSMS?ORbZLX>LchFVD4Gg|wZx7zhwTxa{L-d$axT+70&)!I)$u&OBb$fgh^N3Tbv@?^ zTMa? xnb;JQjZ(iN!&(TE``)1$e%O6eew)F}JDzm6L zrmdH_9AvCT@e^V``6m{iC)ZWY12rm2b=o(>dJdy?>kEu&uZf-}J~+{X{OnXa5A_hl zoUSa~c7II~Cv|td=w1iK(~7ZUN-zk=$3cBId5xQFLQv9!*nqerfNqd@kuG*#^t4~< zsV1Afs(q*4kU;p=(~#AEVOU_@GFbUz>(UXRwzKc>^P%F+G%j07yyTm#IrqST|L4GQ zAP}1SNq4I%C=_w=V}i8Y-AKw 0_vpx9gqD=;Z>|~YyLUlk7 zf7J>Z?P5GMBb$6VVCD+QGT+B1KfO}ej~X@O8f}P{DGypu=(e*fhufUxgKTsNm8~m| ziwRZ_rgApPt#sSsn%&Wu!x6K~gaAW~SUfJ+e-1f1n3gyOEQ*s;OD7td?^dV4sPAwh z38|Z%d2nI^1esgzq ^nlyh#k_fT>z V<_f}nC=d0=zwP;-iCK H z+}xB5{IB>qg *@c3=yCMa&=X>MBmeK><+&Jssvo?K-eKNkeLHLYjD0EoX4jYa(UDj1 z%+)iBl~dfB6Dgj)Eh6YffKmJy{p2v9jqU&AW!@8#V+SvYymoipv*WN>2S)3Vm;oq& z6!8O$`vbkm5B!7&Am=vu^Xx^8bVe-8*FzCl0)LzS)&4&Z7|UsdCf^@kRSBvxB}aGR zsP*adiM>H#q}@N-Ln7L(`+;n1mDinU>d(Ki{Bu3Fl0|$d&ptEMLz@93A}JF;Q9@Iz zJTgb_Do$xXumIuGLGm5h)}FTz)1V(3_5IEwd2D=qbd2dprmZlwJh?zUQzu2N&%GB& zGW>OcRXuwNzkD^wVE3AAexylZmU0hrnaDVN;_V|(pV8emyLgilod|ZXp1vyg-#iiX zQI*{GXa#m&vc u70|UQSSvww+Qqyn9oT(yz?vcZ=cj%1M~~dh(-rJ$Jsm?&)l&S@m}H!p8l&sdZja zZ4y26Q*G@1?AYQ)h*xOHNd2#jO@poR3E3vltlsubyn= I2;P@ z^VI*Wvp*x6g0eoENVa>h1o=UhtW=_upZqA+&&Y`6*Qoc5@|itQpE)VeV{8Qv4phh4 z;ebsj80 Pl4Tb)=@}(L% z6OGEym#DVZ9k5vN8lM=h(u3^oEZk(`P^i2$0B;RN^w0b5N~8&g0l;r?8F{gxV90d( zMxTO#nOU>=U-dp?OwmB_(;p(9G2_&K6PGeM|3KP+5lN6Ido$!ICI5F1U;>qMVk=tq z2&@JY6P~m8YXKpj6e|iTM4Fg=RMI!aR!bO5sM^??{s7eW^_qn+1+GSC?y~!SE+bkL z>ppRpdhGk5E#mqtT*~Ty;N=Lwfp64tj@u22UbREz$JO#gtHwj!>^sM*b4z#AZd`8O z&JI&wDR)(6$i+o8ud0m9`?g$PhaV*5=z+7htPj_!4L0Is?l}41q!t=5>{$@f&S(iX zCNgQ<^0e_3u~IAz7s>e#(L*JlO7&|frw&t3mO__1AInSzxfw^qj{0(>{T@Ae9%a?c zpMN}|BJn;=+N-OxRwM(hO3~cWZqp?()*4c^{W13sz$Wcbn;pEX;;r+LA+$dzHCEkG zL!%&fR&V}iO^ISYWA>(&EK;@4ZQR4+!8>hE>d}buPuh8Qe&+K`Y_x_|bGbJpd!Z?P zHrtu+d458Y2qb$AO_++L)!dlop3duAD)H>a@5vaD*^o3GQKPpOoPuxUKH|-%s!tZI zC1`1DuS8rZZY99fb+?+F&1QHG7SntYB(nY*r!lOhz|$?+Z127PEu|0xGU~*-S*_P- zzlRY+7FN}*+L67{&%tih&P@TArK=*M#UyK&b_Odh8$GW)LD?6`tn;~uKL9s(?TIUj zGRtsRV8E;lYqRUA@XQL`<12||*Il&kFxXH}q=d*4N?3G9M4Ve5`pJA^C|rV+M(^=e zj3vQB`*|9}dnCkGFF3TC&@_gm+p3ZhGVJZN mPp$>FrgxH*Qh@hyo# zAE7*4_@lfSfHO_>7p;b}V5O=vaL!K6+Qsb?0ymH4ImMnBFn84Zi9x6{Ul&{fNh)WO zgjPpK)B+*VZUfFl&0CM##Vb{oG;7$|M;&(l0D@ZZ_cC2UhfVtf(K8cx^i0C39`j64 zXL>3pT@5D(aKGI#{$WrNi!xexx>wHHA?ncBbv1t SJBdh*7zTin%B9mDOmRO%GJfm zL_fG!-5W96jvQW`^Hab?A{6^2MU=kE?aJOGc58L@@7Dv*M ud}zli=%RiAf&3 zP%)A{$CDNDb?QBQQ6oY^_ wT`yQn0G7)xg5OESY4Haq8YCOM4@ycM1 zY2H}NvW3;r$^OJ)G7T$TNSQ+DG&AMywQ9hJXJlWcZ1tNZPuBSE2wTTi|An>BzwZuL z{{XD+_ndMm`VSyhO7VWnJ%kH|_H>-53FhYiMY29wk!t)zCKYZcH~F @;byJpu^Zb=7K9&tr=26IaU{KgmDfoiYf-nv z#-@uhwCpP{lF|$f#5vbcbvCB= VX3?(qB-#Ftq>#}s zomx|Mk~6niN14SUjNG42pSmhRr{OQ?g~!Y^D-u`}mX|lQ;P?sYF!8~&`GGT_v5jhI zKuy;xZJ}l_>2ONsA~r$s?X7zHj;1Jf^_tPyzC$2LUWy|C1SrPP#Qcu^0skB4)NaAE z>u-k6c44+wqLUu6LD4W4F(c-EJLVH;qawJW270h;XGWr^V?9ZpM)Cm?_#>ipPP10f z>BY|v?q4cvKl_fnJd#AbcBA(1Fz&ddZ n zy}n>XxIKH$uedb(<5YSy7F{b5Ad=bYBnn5p#XlPgGQ16WM3~5?RZ_EGT-SHF+MTeN zI^f`~KnVHH^ip#qA`Y_hvm!ktA$MnZ_)4rmrr@;|vmKFrd>CfKoFUb4wrTIKfS;fV zWd5dKaJw(v{6j18g9m)u)!A{FX7`f+ue`?_AENgzLwaoLom0lU8Y3Q;L=vm5!xy&l zCvm7te>N`IVGHNg3yI>Pnm+(~i)i2>xso%c^~l+HH0%wnTS?V;=Axe)in^YC#IeXW zy{wk+q*mztC|8PFCq<{>sHDE7uyCm9TuzjNhF7A~JhymE@G;lV5FmFvQ6;=gY|?tE zxiz$L6yj6XdT!_lAPs$nk3Y&+_~}(Un4=e_p1;)(w%eZ?9JTd{GBuKRFn| NdljF3f4p-{ zE?y3JGV+j+48r6wQ<>nJyL6taald{^dm@kC4aN?7_c>=+E6jY22vQVzuI^OC#@ e3*O{dm zq`q-$bwhJ%xyMU;9*GT8jyi*J)9L~{$6yqCB*4D)c5Ye%tyHA(AzvsdhO%q|&3M(e z^2*BW?9UtYw$bp!`t;fpVWBwMQH0qV!(|};E?5mtpxw5&mQ7^nVO zr?t|>M zRSh1eH{fSuJ7Y^1l+>}*BnU(Uk52S-TfXd9tP9C|AwvzJ(3-WVvL*M#UxVP-iE5u{ z*+hvrYhlG3rBZ~l1uIov2_Zt=Wb`UU7I0VaU7vjteBkX-dVQN}!Cw;UOQwV7dDYxd z?xMjzA9tgjDy^kCj@oAu6e>dqT3R9l4TiJ|YJg?5@8M^yHIx0+lO!_@0nW9p>3F}J zVXAr2@L9d`ri!x`!zA!bk@y+ %tZu0yM##K41q8Fs;|$;{&FB@BZ|>N-J=C4R^hfN9`1V&M z#A_-mU$pXfwa;zrsqLc+RlGd77Q9f+ukZ+Yqw#a0VRuERa=Ps7^R5jIwXpl)>O$i% zHSn7O7ieOx-d{qO)_ QKc^gsf**v@2PCP5%^R=cdE{glr%j_=9#OB2c_ob>r zupo`vtnGCJ$#|zqf<{))xskn)FYX%w*krm`G+{| ioz9QMeDN;$T3N>(lS3r!xBYL*yuC@3 z_j-<_RF0e6G1{G6OH@kdw#2HpDBrWta $=u)(>343q~3AdC|@QWc*q_60ca*~?HJ7>&m{)-IxrjvT_@r=wn$xU1*pn` zv=tC#gVcB;ENtdo({!x8*0Vr)5vu&0guC{5+!n1377bg=yToMwC+lm*N)~kfMK|+v zxOdETb=F^Hys7Eu_Lf~d6K*#QR2fLzieZ!>WQh=e zAU8k5Jf7pN$`kcysI};P(AadY8N3gLi!@o~7 E`|#V#>;%7dj7a^XMH6g z72_YNp*Yj^Qi1&hEWclX)e`}JdZic}MlSuiWLQ1nf+;r4R9kad+g?!6?X{zUd95z3 ztliQ6sgS=*wbJca51Us~l%cvX5t&{-oG43J-*l%xlaRjrWWD%8iRbAX+hON-9A`95 z^aN)b=Cm)d+7(n 9PeL{?$DK%QGJd$ zz|ibowpuiWs~zbrFx$A;g?B@!GwJDtm(aas_QM7(y)c39DYN<6>!E&> w|K&)8b@Bt(vdBW zg=0bPo@00Iif7;qJRKX`ovgXWANLZwVcwn1KJYD{-mN`R4Y?xxep`+l5bK5@;6P<% z`x8-uM_MPD!VR|!N4_TGG`Uo+(?fk2e3<`{SgUuxY=v!5mSqPb!U&(B>5cD()yWU6 zT~JCN)RrbkAqQ>>DU+bXaGJN=$s*0|cH=EYR0?43p~OL_ggh!kwF!Oh$yk$#ZD7j# zw-%E4ypx8V(c;ZLG-D2+c*M>mZFV4+YJWYNy6?bSJ6s(oJu@=V(q8t|`OWiuJ0=!j zh}kIA`g!E)(`E7z&piCnNNnu@kk>sRpOyUZ1a16P=&8qy;?60si4l=hu1zl{Vz0j@ zsVYkm$^gBcZK}VdoA`7?p;c47Tuym6G @ z2<={abO7Mi0 zI>(6JdA25&I-sio VPmJ;{vlM+tqtaHx`+^V(eC1ZV!dL_@$Q+QOaPF=~h)UZQ+gDM6<6=uW|O*{oRxz zk(=PDI?F1_8n2c+xp4%~Vl#IncpI*9ejh%r`ejRSc0&n6o-tP=4Tt+J>BZ5$( YJR#AF>TA0zazcp_ zn^4Y*s@&uZ112P~fg(L{YH{8BXMXmu?_=}u!s2CWNBy(5qR`;9)nW>}*wzR05>U?f zuHR8^{Es 3^^vIKal fy9P5{)s@{!zRudVKyXW L}kqP9g{YRJkKgq`tgMCE)n8-T=^)s@8m%~HsuY#YVCEkNUf;8BRy+l73;yuBe; z>!m}r&W>xed_!=1KZ%%~Zkvkb@JU `k)Vd|+Pb`bJ#qZbsxaJ_3p8f5clYYBcli&1 z)Q?GrvRR1kMmzmBeE&ZEZLmY_ae>@6nM-5hYiFAVKtz92slNaq$MsMECxn_rE6wz+ zP>5q=<(8YfQ1(sWGES$3o*K{0O2;sVf8v*aq_Zl5_qKxWQ218WfIi|b%=<(H&e JhlFqXyAP&&a8Gt`7>R3ppQ^E*Sj4R@TG*xkw z4*dIpJvDKLq&7UcoaQVDp7Qwh#H2_6C^4zz%^`qTHaK!FI#hM3g3Mbo_2i~>AJ|6l z%GPyd=4a;b>(_v*N`yr$TwRJ}6P_~GGX9MGx^5t`F{xz$4RIsn7w}@U$qSraZh=;6 za!tl~PFNYRl_k-a%w8GM57`sqcJn4THDCA-UDf2e=vO*VX7zGjdsCF0GTz8tgo=u0 z%P86Ea%Io7IiKhq_f~@DdpOu-Ir L>}P(jjp@Mg@#We zri1nPqon{-eRF`FrQ+B048ja0=Uk t4eQ=hSqazH$BG7rzYhrD9_AhZqD7_|7|($XQ^~-pJtaG&h&|{li%d5 zdN~<<{{{JcBj4I%<)XJ64KdFc1QW qj|X+&TX-`nU{#gEJd7A}x?c;+ExSL0^Mmr8fa=Cy-Uy##3@4qZsE4Y6XW z;%XH;>pd=KAgJKmPJT9Hi)P5%l6GUzMn&;~PFoH_GpXpE+Ia(#wa#<7-uA;1FL4fm zr#m f>(-POy8|OGrvr$#d9L7d9W;sQY|RtQN$AsBsG2p zCfB!%)>xPMC>$|CdM7>-ou2EwQHj0N`i_l4?i$-Kp?7!m7I~yFO(C_Ji@m)iAHZDQ z*FtJXwTLRcC^~R8Tv$ENPI !fD9Dx zHxzxh^H|xAt?4gS$5Np$0%5#vdgY730Xb{M&HCCyc--6NIkq2H?i9L@+{{L+72ZC| zuzjBQ 6T(L*aA5G)CarXWdpUqR*r&rISf;b_wJP zs1pe;rLY!LUsmb;$8r55FBTB9f*&J{)K0{Q7<#SetUPD(bGkjLGkH`_mbr-rE({nR zkJNV)EXfx^4O|g42A?Up=5;lKCX4JJrGY;b374qc39-~#<&Y|63t*ozgd$yImesMb z$psDx^Qt1@-6c#MDSr3CXVe9o+Xrrqum8rFx?F@yQtCT3{P=J-P#!e16D4hkc+qKS zHugdhacbh)f|tuw)x{LkGAKIec6?)_U&clvdOVTr^xKuv=k*I|E!K8zHo-J|l} v|~P!@S)^ zN1s5HMr+#f?6>n&sjcEQUks7663C_C|4~<>i2G4#QdO%>-l((GiN$3Xzcuz)>}NDg z4%?Od@`*-4!OluD-*|}}_*wMneuuloi8?xR(zwy>5dVc1OiQayFIda0I!7zP-mm=W z8HFg3NYC$#}893i)o*P=R?_P?Y4B%5CiIX>Y_RjH!NOv09E)|AqcmKRZLq zOmotQ9C34wcw6{155XFLIh{7OgM#>F8>t@1tdt|5GH=I8mB}Q$E@P(-qo!*ILr$v{ z@@CN9gc+s?GRvbKtQ(%krHckebt5U-pqWQBq1``CD%HDGbypi4M16#)1)djIqfr?# z1P|&1aF{ayG<~2r+i7wd1%qsY5$?=Dot*?WCiZcL%0j*7MRc8x@{ -tD^3Ep(nUJg0cIq`$20312bEtuZN$;>=&!XLB G+ce;8dKytd)Q3kA N=_Py&_csDZ5k%>feQ8heIHpsa7O8V>{`H)a>1WtGE ztsgsDrF`Z$83*Y_( 3k}WZWbK z&{LLfHSU2CBTDCz?@Sd1G+hg3@5Z+Vyb8euO_tT6zhCrjNlTq%tlOfMDH?x<@M!t& z5A!ggw88#_LOX_Q)QY`RN?=yAa%3q 1P<|02 zA>Mnpsm+rh`sZc7jT)k1PXOTECkB|&a%H1-bdIl*71;clpJ19gam71)rn6i?7(2Gj z(0rBWEZdH9N*OS#ByCl=FDqwqQ#_(3xvw?zkIpj%^-7YAd(x%Mei>pId6l?EgRM<` zRbokptd9hV0!z;hM3S;Lna`@_(kpkO^5^f$b z4w+L;*ms z@*7hqt_jb`gdg$a0&N-#E4Q;1iR!0R;g3i#7!^-o!7X92u;Kgz@T?N7{fwe|HUS}u zT3GF!E4Rs6(Ink~)~V>0t)oagVc!zvSFR^nrSok+^ir?AHHmAf=nxHJFa6>DUhu?8 zcjS}25DW;P9BOl3Gu3igi;uK9KiK <2HwyL6uD2Hf? zh|S)@j_&Z7sAA&~%X Ij#NJpjgj_W;Ri*2q z7Z@pw0=qe7fNiOk`wMH%9s|PC;;FA&BED|2zkl0LDn%&Zt|j@zL l`Motcs4pwbC=u62|FlgqCxA^4XUPF)m?b!cgh>!D(9SN+s9e>~iDToD7 zmES}BidXJz)yw jL zI&s+KUfSnkuf8ltitwM}>&bqCjmim|KqJ46a=(W^lM1HC+-rAtuStI(^(=gI-ErRi zq%s_qnuw%&YzmG3PPMDnS1LdzYJKF%&ExHxKAoUZF05YARed5~1UpI1T#9O-!Jaau z;tl3Lrz`YI`$QNaW-vRmKye;RXWhbF&l0x-l(F RYzvIWjk8DJ=vi}#J~lNMiw$%s9)_w=o@P?Bzn95ChgT73=b zSxqPA!`@HZ5pmVpZ-gma><}T!HC@}9AMwDFh@SZ-iG%j7YTz< zwzuQ*#lx;l*;|GsV;$c5Zr{Ja9Lx)Zejf+hKDKI)E>I5)5c6q?68V++tsLj*wmgRW zH4)3J@lUH&O8)eN7O>I!no@2Sco9^g9X2yY0}QIojd!|Ny8$Bcj0tvvmB&hcyJj(> zP1vd8Sg}8MT<6f~wJwk)mhbyi0+bCslikMnv@xl`x$x^+uu$j?;J>AJ8Hvt@&Wp=` z6QVG3HZ5hRZDUN$?ehKrW_EWacE)$eg>)c}Ur=7h97_(vaQgXy74li;ue}>Ei0N#K z#1i2zH?j$hBI;O;;6{remsLFLK3h(dz0Yu`MN~3)1YoNCKCXVW)KR291JL_oSy5n> zqsrUx4$tm-05#?u3F)>u_EDm?;Ull=qlBV6y&!-hmo5X|m+P(#8jz)@9_}1b6G>fn zpy}?j=1ZzcwII#Bn$iV(!X;(l+bmWcJ-8anw@4^2T}pi@zH#%XXoe-!61}cm()q%Q zx87pAn*M?WT~9&3rAr(iYxL+GwOC()_yUWy^M^0#eZa(JT=o~G=uUB_N2Y1=Q`ftu zU!*_7wmvH3QeW_}D{6$8vsjGpc&l^pJF09F*9wz2wCC3#njyjVnnH! T*@=4^(nAnR;;64Q^L#JH!VHx=xZ9vSkQ(Up%asYsD0_x#%uG_0A?pw(*!X z`hZzI2GYbNnLpYstytDvNM5?MJKt~~H&$4j$Gn$zwJ+C5BTw@h^%apstjFXg!S?YG z>9ItS5+Tk>t1+AAL%%#DC@NBLv@r8Uql;6hQmfXg$n)E;@Mm9%AC|)uBlhjdXw41< z_{Wn}tCaSCpt?VlBu=K8j3ISwA1C3WqdIPQ1|;~?>4io?o%Q+DT_X eJFF6TIbwnb%)7E@4; 9a+Y~f0VKwba=E`RzLa6~8 zhu!eLI+8XkB4c?nr4)9Vsk=9eYL4*|er}vKbL`R80ak@sCCnS2*O&7`l+;7~HU0ps zhkhB)g2xS4Pc3R`@Ps_sxB HKKA3oqr-BrV3vEVy;+|`!2WR6XizOpX zWf_j)&-~wWmS05#uXX |EcOcsSZBb)>begB779_{FuFB I}sf%TppWew*OOmwjD^t%?nYeUFJtT~#=zq)W`qR*A&I;P60|#l0w<^Pa zUiY$(I=7j$1y)pKHMR@rHsazf-$w5Y;9>+PdSw%lQtc&!j&;3BrORd2Zkx2Zme}xi zxQ!*l&4s61e#t|a{9*HDTRh;6N)Elk%0Ga({%#v_qbE^yNPFiqc2vIobShT5w(OCq zuTxZK4GE3Rj_fL@)z-Kx>D0vdEOIUa#H0LXt;#n8f5OTLI7@5mJm(7LeQhN~u+GA~ zN-6VGr9V8xlwDlYWiZ_3c?F4JK}>?l#9HrQ=T#=s0=1oigve (3JNyMn7StMs{&aOiaG~ikE zQdP(*9#m#JOOZoyVExK}XIpq`9$EZ#aSpk&=juIi{iwiS*%jTQU0G6|S2ubfK{#(3 zM=_TsEPETcl!ePE7J=3%!jGK@Zrl-!FMJ`UpquJ@daJ7TX|THVmD`uHc``9D4r+Ta zLYz&Zbz-k&$Q4~susv5P-cry A^!u_x@yPe{{N(a66v{>M z(HHw)@rpA#Hns98zm=$fD_Ev0zIIv91Wje1Y!<613B|3%?kaFclc+N9qpG>%n+>We zNTw@glI~dzm#hS~-_e)-o5tbZ&)RCpMfC({eGgpU5tcja_$j`AY#&-jXD?(K;a2YV zF6ml6?7b-X3mg$fs?XiHyBvl~7WG0jg^XZNNIWBfSH%FPMAnc5^-L_dQI3 PbpjozF;SJf;@)V7@&<6(f^jB1cY` *HhfX6qB0O0GEkn>l$;b9-JhZJG#+ z<1L2_yuy5qKS;)c>(RtdC8GdVT<_bItS;e9>00k_$MVeTucZB~rzmRCETqit%kT@P zAvc=bUvZgkKaGMXZY?|wZmvW>AlcXB@UjSLHJhB=|53z62QnMIqK3-J><(}1n!N^N zAv+Z79=lQNDtme+u6` bzoMf#vuKyL${a*bbr0`SXS0--6s(+SL^bSkNy{Qn z+pxAzw1TR2<$iZfWR{`UTaZs`K!>0be|7Dn10IbWmF%BU5oL=1lf~_bi1#?62|N00 zZp068p2!(KFmr##`(zZ?7->0-@#4i_2J63QtpDr4 98(sPnONmb28Fdj8-oNBY{{N!| q`FAw>pyLW6FDuZ&}q110$Uh=k4dmUmyG*dFlUet~$e?>HiDlKrJ@_ literal 0 HcmV?d00001 diff --git a/TPSI/costanzo_francesco/html/esercizio_html_12/costanzo_esercizio_html_12.html b/TPSI/costanzo_francesco/html/esercizio_html_12/costanzo_esercizio_html_12.html new file mode 100644 index 00000000..2689dcec --- /dev/null +++ b/TPSI/costanzo_francesco/html/esercizio_html_12/costanzo_esercizio_html_12.html @@ -0,0 +1,66 @@ + + + + + + Sondaggio Videogames + + + +Sondaggio Sui VideoGames
+ +Come ti chiami? E quanti anni hai?
+ + + + \ No newline at end of file diff --git a/TPSI/costanzo_francesco/html/esercizio_html_13/costanzo_esercizio_html_13.html b/TPSI/costanzo_francesco/html/esercizio_html_13/costanzo_esercizio_html_13.html new file mode 100644 index 00000000..8fa1370e --- /dev/null +++ b/TPSI/costanzo_francesco/html/esercizio_html_13/costanzo_esercizio_html_13.html @@ -0,0 +1,39 @@ + + + + + +
+esercizio 13 + + + + + \ No newline at end of file diff --git a/TPSI/costanzo_francesco/html/esercizio_html_14/costanzo_esercizio_html_14.html b/TPSI/costanzo_francesco/html/esercizio_html_14/costanzo_esercizio_html_14.html new file mode 100644 index 00000000..df4c4fdd --- /dev/null +++ b/TPSI/costanzo_francesco/html/esercizio_html_14/costanzo_esercizio_html_14.html @@ -0,0 +1,125 @@ + + + + + +Sondaggio Videogames + + + +Sondaggio Sui VideoGames
+ +Come ti chiami? E quanti anni hai?
+ + + + \ No newline at end of file diff --git a/TPSI/costanzo_francesco/html/esercizio_html_15/costanzo_es15.html b/TPSI/costanzo_francesco/html/esercizio_html_15/costanzo_es15.html new file mode 100644 index 00000000..2c3cea39 --- /dev/null +++ b/TPSI/costanzo_francesco/html/esercizio_html_15/costanzo_es15.html @@ -0,0 +1,58 @@ + + + + + +
+esercizio 15 + + ++
+ + + \ No newline at end of file diff --git a/TPSI/costanzo_francesco/html/esercizio_html_16/costanzo_esercizio_html_16.html b/TPSI/costanzo_francesco/html/esercizio_html_16/costanzo_esercizio_html_16.html new file mode 100644 index 00000000..b8785ddd --- /dev/null +++ b/TPSI/costanzo_francesco/html/esercizio_html_16/costanzo_esercizio_html_16.html @@ -0,0 +1,122 @@ + + + + + +Esercizio 16 + + + + + + diff --git a/TPSI/costanzo_francesco/html/esercizio_html_17/costanzo_esercizio_html_17.html b/TPSI/costanzo_francesco/html/esercizio_html_17/costanzo_esercizio_html_17.html new file mode 100644 index 00000000..e2187d60 --- /dev/null +++ b/TPSI/costanzo_francesco/html/esercizio_html_17/costanzo_esercizio_html_17.html @@ -0,0 +1,252 @@ + + + + + +Document + + + ++ + +
+ + + + \ No newline at end of file diff --git a/TPSI/costanzo_francesco/html/esercizio_html_17/immagini/logo_agnelli.png b/TPSI/costanzo_francesco/html/esercizio_html_17/immagini/logo_agnelli.png new file mode 100644 index 0000000000000000000000000000000000000000..9fb8f83252435636cd5dc589819493fc5a78dbcc GIT binary patch literal 12823 zcmb7rWmME%`0daQLyvR`A|28xEmG1QBPrco@&ZZ=(j|?QNJ=B!9fE{_(#_Cu5C3)V zm;2$ab$@FSYu3z}6Z_eFKhHVmgSx5$9ySFw1OmZRQj~oIfgsU=|J^as!SAQLhcn<0 zmb0S18w7&i{rH3QnGK&3yol>Ar{`|(WNiyKx7UO4333mh{P6t0Ue|~4@Cz4`RgL|h z*WKW*mX?kXOIdXe9#Un4JP3piq9iM=OD%Q{NXPp7@qmzaN_(D~h2kSo&N} zO6UEWTnI~49)nTRCZ~~+i_gbFhS0T8WZmhgXAIci-3Tkq6lJ9to|$9$DJo*>_lxi$ z?uFddygbHUkG=iwa&vPv&64(YXJ@BSRX0n-+ + ++ + + + + + ++
+ + + + + + + + + + ++ + + + + + + + + + + + ++ + + + ++ + + + + ++ ISTITUTO INTERNAZIONALE +
+
+ + EDOARDO AGNELLI di Torino + + ++ Tel. 011/6198311 - Fax 011/6198421
+ +
+ E-mail: agnelli@agnelli.it + - + Sito web: www.agnelli.it +
+ CODICE FISCALE: 00493420012 ++ + + + + + + + ++ + + + + + + + + + ++ + + ++ Istituto Tecnico +
+
+ Tecnologico +
+ 10135 TORINO +
+ Corso Unione Sovietica, 312 ++ + + ++ Liceo Scientifico +
+
+ 10135 TORINO +
+ Corso Unione Sovietica, 312 ++ + + + + + + + + ++ + + + ++ CONVENZIONE PERCORSI PER LE +
+
+ COMPETENZE TRASVERSALI E PER +
+ L'ORIENTAMENTO (PCTO) + ++ + + + + + + + + ++ + ++
Prot.N°
+ ++ + + + ++ + ++ + Tra + +
++ + + + + + + + + + + + + + ++ + ++ l'Istituto Internazionale “EDOARDO AGNELLI”, con sede in Torino, C.so
+
+ Unione Sovietica 312, C.F. 00493420012, Tel. 0116198311, d'ora in poi
+ denominato "Istituzione scolastica”, rappresentato da Prof. Giovanni Bosco
+ nato a Poirino (TO) il 14/04/1962, codice fiscale BSCGNN62D146777N,
+ e ++ + + + + + + + ++ + l'Azienda …………………………..….………, con sede in …………………………. +
+ …………….……- P.IVA …………………………tel. ………………., d'ora in poi
+ denominato “Soggetto ospitante”, rappresentato dal Direttore
+ Operativo……………………………..nato a..……………….il ………………., codice
+ fiscale ……………………………..nella sua qualità di Legale Rappresentante. + ++ + + ++ + ++ Premesso che + - ai sensi dell'art. 1 D. Lgs. 77/05, l'alternanza costituisce una modalità di
+
+ realizzazione dei corsi nel secondo ciclo del sistema d'istruzione e formazione,
++ + + ++ + + + + + ++ 1 +
++ + + + + azKKQ5WWTu+3#XUAh)S)mf3`0TfyfTCae NwMx5F!uZXe3Wj=WG6>u^{Br%|z8=0oxgD?^BiBpddPd*(XkCA8~hxqml42oOej> zJka1$L&-ZAH YQZJcf e zHS|iNH+>!g%ue3+_>?JNabQzk;m%Ctca-aQG_1^ucQSrT!5GfKC^tY8yBFfN#D>xw zye9W^K_J~fY0Q%_P7LwuCY0At+x$RLVeMGsBT< 0QnZ^%uCMXMa zZdKD?xynrm+;?Pa+)v(>M@1qGzlW(!{5u`Hf}y;p=xRsCq-)M NCW}flu@-c0WI829j;}J!E}g6C5i98`%fR`kRbGZ$Zi#e zFM`3iuil~Hzd3dHs~7;v(&FGV_th?fta=#_2b+4=r?l(oj0#&ma`KahO`aU+2o#N! zt=JB!nGMAmwD|tftd9BW7mWTzs%TcjbbhGSo%8kuH9i}JW``!0fk8FytlJH357~PR zJJ@UN{guZ4AKy{oH>KqG|15^VwivnN g8 zjf|K{4PH(Xh1ZHIPo<6Yw|@lAgj~Mn<<0DkSU&liGE>$e$UWZShlDyFpKq=99ahQ8 zPIgGrW^V5P8ga57*HJSz>&SS2Zn)xSu{kz1KGTtlKEV>)%~gKs@o=*eQqFFfy;D@H z)!qTe6> Ks9SzHi@{ PBH17g`~ z7h0-0gNVnFHe(ktpdO33y9p?3_KxoA)bkOB=L8Pw?auC;+z~F+YRp!ZC}#EL& Ec@z3{zoWM<|)-zkfxmONnZqn4A4mXj?R`tzQwswHo ZWlkN54md`8;pw$mwTm2y;vdG0j{(mKQZ?0R8(+ZG(1=z^ z`#C?5sMRp|s@HQrFM dVcCI>iI;2fF8Dsjqk0|FN;ZEqAl_ z@R=dB(}W;J$56=8igR>ZuQ_wqdvU>ID9hri?7R Fy}I(?S(RFb9V#{U^yz Vn>iWNt<}yn7%)dw(E~^9&sb+uhUWY z7W;~gGRjR b=cC?cS+FO zPsJdaqoy(0P~}FyI{sylpCg$gKkaD+dQndTV@LW6|Gm1A@0JIW?D_KAIb7v~udd^# z3q2ww)&eQAc~-ZJcO3~(=oT{^7IzNbga$oiWO{oYjuu}={D-r27z`PAuk6PY9Jes` zqCt7iHZW~54D-eK{enLuhJ6h|VRpW!G_^32G38W^q^%<|!jjDC@$Z6#K=L)7?ym32 zsjY$k2t~l*%{Aifn_Nq(W;;?uycj(u|A?e36O>%xf`Kow@?lk4qT$nbURMt>2a23G z?W=unqj@%A_21&F sZ9jfQBlb#1 z^I7=qy63aJcm>{(!EwlW&o9>tz99;x5zJ>ha(wOv@bj K&;)c@ng=_m^EhjsWpN z_nKJ|1na%qQ>J%kiPw4+W_7&h|1uUXIv1O+zM@=j5dU>yaBUr#t+-yf!lO*G YQJw+kw~pbQ@!ha}$CsHfm(4 zv9X)%T`!AJMH@F2NXWAl6g`itutx5$!!Kz}ofWuxUkx`lRKr1LRn)E2YWn5e7eR~s za2fGC{nO7PmD BkNwL(^(zKkcLm)= z#g*zdIvSUj-ltvhW(-Ky_T-(QG2A)vCQKfTie}jwprR!lrHN=8$I``fU!7^v3I9qf zk~5=geHIe3;6Wtg%KO4B=;)yN{+Nmm+fYMo{ljwWj0izgj~fc4|2QLg9J=eg7B)qk zEowD9zA0bGNr%ZqC*rZDIUP9|bWHR4^Ta1qpbW}Ug;$#l3~fQ0#dadcZ{m~XmFa4; zHN`vXASZK!TVG^scj4mEPrCYqu&|N;4b!KT9Yn?!We-&}oUp21Bl27SAh;c=XxAyx z(6Wn%5Oi&|l!BAko?fV^kU7(_KB5-5AO}8Gu5Yu&5SfI0Mz;8NRT;W2`NaBYVXfA$ zBjs0OT$A|tMTk&eOnlGl9Z$KywtK8#k;q-aqur`2*h=G_r$p}y!KLm#A^mR=`Fd zE*B{X)|W-cb I?1Es|D-nHd+E%SiO{HGBGyp&uXnNBbFxOD3#YtQdcrMykE>DlOeGoTo*_ zIOVaE{gU^mmcoi}-v!Zuavc_z%EBJq+n2~(iXd6@X<;3swf~LTa{ZikSG=%rTGT~B z3c~GHbaTDp%l0iul6JTI4`ewoqv&&;kY{w9##C{f+hqU;g9$mjgRA}7RBiu&%bof3 z+M1k%ypr61)_l<-(e;p%VvS#;S+(@7qTO6 ;{}Vmd zpW7bo!zsuW2L`?pn13S18obmAdvWWwc}eng&Xj Qr$i;ezp*oArG)){sG(A( zzTzSkj!T!R?@|~QE@3ZpD -(=QYITvG1Y2je61`q~o@TS`W2Os9B&!)tneCF-k?gv6 z(o&EsvHP2qQZHS7tk*fJixZ9O4J$U7YijlONX)Ot=WZs~ZhgL2p3CaN@QlT?inZA; zy10YG{*`D9x>Df>kac-1r6o&O I!z%TaSN>vY zjIEYlpo}9pOh@~!doNZ{4%^kndb7BvUhX+Of!VB5g?`{dm 48A zaxl${f;yWibnm~UE7|R2AtC%jTec;}3NF}m(z#LN?-n&kz0rzhUg P@-Zc*h`BrHVzka;DMksJ zy2qCI?`j)Dyoj^k9bPLl*+l=8R6X076`;>h(I?M2A5JCxV|V0gInT+|BrLvWY-VfT zANsVV1{VS<2J=`=>rZjrA0JdNC)b zly5S J6n`#P-4dJUFuyQt+-(iI{KuE&T