From c906b4e785b61d8b15f2de4d0281bc355447a791 Mon Sep 17 00:00:00 2001
From: Viviani-Giorgio
Date: Tue, 28 Oct 2025 10:41:32 +0100
Subject: [PATCH 01/49] prova
---
TPSI/prova.gitkeep | 0
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 TPSI/prova.gitkeep
diff --git a/TPSI/prova.gitkeep b/TPSI/prova.gitkeep
new file mode 100644
index 00000000..e69de29b
From e5a5102386e3d46caa9077bb787ced9ad6bfcfdd Mon Sep 17 00:00:00 2001
From: Viviani-Giorgio
Date: Tue, 28 Oct 2025 10:52:49 +0100
Subject: [PATCH 02/49] Delete TPSI/prova.gitkeep
---
TPSI/prova.gitkeep | 0
1 file changed, 0 insertions(+), 0 deletions(-)
delete mode 100644 TPSI/prova.gitkeep
diff --git a/TPSI/prova.gitkeep b/TPSI/prova.gitkeep
deleted file mode 100644
index e69de29b..00000000
From 3853235ce6e98c62cc0c311484c2410b23dcfe65 Mon Sep 17 00:00:00 2001
From: Viviani-Giorgio
Date: Tue, 28 Oct 2025 10:54:01 +0100
Subject: [PATCH 03/49] Delete prova
---
prova | 0
1 file changed, 0 insertions(+), 0 deletions(-)
delete mode 100644 prova
diff --git a/prova b/prova
deleted file mode 100644
index e69de29b..00000000
From 7a34051d88b70aba2eadd44553f3a642752ddda5 Mon Sep 17 00:00:00 2001
From: Viviani-Giorgio
Date: Tue, 18 Nov 2025 17:46:36 +0100
Subject: [PATCH 04/49] html-01
---
.../html/Viviani_Esercizio_01.html | 23 +++++++++++++++++++
1 file changed, 23 insertions(+)
create mode 100644 TPSI/viviani_giorgio/html/Viviani_Esercizio_01.html
diff --git a/TPSI/viviani_giorgio/html/Viviani_Esercizio_01.html b/TPSI/viviani_giorgio/html/Viviani_Esercizio_01.html
new file mode 100644
index 00000000..50497cf5
--- /dev/null
+++ b/TPSI/viviani_giorgio/html/Viviani_Esercizio_01.html
@@ -0,0 +1,23 @@
+
+
+
+
+
+ Aurajacket
+
+
+ Titolo della pagina
+
+
+
+
+
From d6c7c00f8359fc17add9f8f504f777ccf910d2c5 Mon Sep 17 00:00:00 2001
From: Viviani-Giorgio
Date: Tue, 18 Nov 2025 17:47:17 +0100
Subject: [PATCH 05/49] html_02
---
.../html/Viviani_Esercizio_html_02.html | 70 +++++++++++++++++++
1 file changed, 70 insertions(+)
create mode 100644 TPSI/viviani_giorgio/html/Viviani_Esercizio_html_02.html
diff --git a/TPSI/viviani_giorgio/html/Viviani_Esercizio_html_02.html b/TPSI/viviani_giorgio/html/Viviani_Esercizio_html_02.html
new file mode 100644
index 00000000..eb4b114c
--- /dev/null
+++ b/TPSI/viviani_giorgio/html/Viviani_Esercizio_html_02.html
@@ -0,0 +1,70 @@
+
+
+
+
+
+
+
+
+ Esercizio
+
+
+
+ localhost
+ 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.
+
+ Loopback
+ 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.
+
+ Name resolution
+ 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.
+
+ IETF standards
+ 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.
+
+ Packet processing
+ 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.
+
+ Special cases
+ 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.
+
+
+
+
+
+
\ No newline at end of file
From b4aff5d732bec654b154373b02bfc8fa5ed2e477 Mon Sep 17 00:00:00 2001
From: Viviani-Giorgio
Date: Tue, 25 Nov 2025 11:55:44 +0100
Subject: [PATCH 06/49] sito tpsi
---
.../Viviani_Esercizio_html_02_03_04.html | 70 ++++++++++++++++++
.../html/sito_tpsi/img/download.png | Bin 0 -> 4772 bytes
2 files changed, 70 insertions(+)
create mode 100644 TPSI/viviani_giorgio/html/sito_tpsi/Viviani_Esercizio_html_02_03_04.html
create mode 100644 TPSI/viviani_giorgio/html/sito_tpsi/img/download.png
diff --git a/TPSI/viviani_giorgio/html/sito_tpsi/Viviani_Esercizio_html_02_03_04.html b/TPSI/viviani_giorgio/html/sito_tpsi/Viviani_Esercizio_html_02_03_04.html
new file mode 100644
index 00000000..a41629e1
--- /dev/null
+++ b/TPSI/viviani_giorgio/html/sito_tpsi/Viviani_Esercizio_html_02_03_04.html
@@ -0,0 +1,70 @@
+
+
+
+
+
+
+
+
+ Esercizio
+
+
+
+ localhost
+ 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.
+
+ Loopback
+ 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.
+
+ Name resolution
+ 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.
+
+ IETF standards
+ 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.
+
+ Packet processing
+ 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.
+
+ Special cases
+ 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.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/TPSI/viviani_giorgio/html/sito_tpsi/img/download.png b/TPSI/viviani_giorgio/html/sito_tpsi/img/download.png
new file mode 100644
index 0000000000000000000000000000000000000000..4db25b345844537de3383f1799d2a4202f5dafab
GIT binary patch
literal 4772
zcmV;V5?k$wP)00024P)t-sM0uhA
z|NrKREQv$V>OGR!XVAa}M>w4Pl
zx9$J`V_zl#6b*O8K7F6(oLymS^OBj#%w#eMVmrv@#8QyZ8c4AwrrdHcLMtYQ?}aLE
zPX&P0(DRK}d|Hq(Oj~!9ZkRAAj&7UA707^mshv`xbksJ|){u-G*gEb=zOukrw}Xas
z8j&HhqIab#96GAraCVxIF(wwe7!^tfS(7HJQ=g16wS*3AaWRl!P3zOCO~&+ui_S^{
zEO_Rn$=G4%7Ay}+XkU~}5ITKP0XSiBF*4dDytuMtfx?M)5i+tlS9;NwV_;=o!%9~s
zV@!3m=Xn7jRj+Q=s*=$rLT{R%g(6fIwTff{@3PBe5is&9+JQ=BWM5aWMFpVhekH}J
zL}sdAZCV(xKJAE%>|Wk|DFYJR3UgCV#&FTqxezwUEjMbVWVHE}tk@}(d8tt=Bcpk}
zIxt0WyfQW=WK6G%)Jr!&N|_&BOvbc+h>S5PRxz7GGMeT5n0Wyp$10SxA~M-b$Y|b`mr5RR5u1E6+K*UYPC?e2d^Wjc#Fff8PuG`lS{^Me~d%Mhr@TFd1Pe!()xlh
z#;tw_vUzI5BjaB>0jq?T72-DL5(|DcGKPL(tE_syY5KOMw(yn|og--HWMuckTrg2z
zA|$frxAFZHP8@wsX4~Po`NOb9-*X|~V%TkRq}y^brgiBR25&`6MWF>!@2mg)_u?o`
ztN}i^&u3&VAM%r#nG(~F9k%w#=5%hM26U8p8JQm37{!uh8o?^+Rwf|7)d<}B>Oa!Prygg9jN$g=Un18qEjsWpq@S_i5x?H7
zn+R63K3ay1-&+uars5QS8M1i~teNVNvdjcpunAf)?ZZ09O}5BB+FD^ra|*^nUPZ+@N13ZCE$^fdk*`jykr)7A#Ap_rbd@JWc+?}
zONwjoj3*L^6{xjzEB-kd+3S}K3IoIAT*sCMN$%=jqro0F}wQnO%gSXOpPDx5b8v<`OzSRkXrR9
z8X@~YM(!)Z%);?=-42NEYh+ecCTGI+q)Z6Os+sfjv2KcH^?j9C&M28_*wOH6fp}qB
zZqbBe%XO@CI8DeH?p5|L70+M~pQo@2@i%L@i>!bP$e2Al%rTU?5daw!>gP8RCLUUK
zf05M)0U5t`_N@~rbD5F}ZJQ(Juy6*IeJq+j05bCQI$Qp+n5pCsp2x5HqETIBl&MU~
zX!GlAEt6-jIV|kw<+yMt)-Y%))Cm$Y=5?fu=FFh7$AAM9oFTlBshO)4mvi!EluU4~
zeR3s$Mbm|C4er!fGOrDS?DF%w>O{D75o3EOx=T-1m$6Y?;U}IeIRPR|2vl5^_%qlOt`-2)079V)o6yC9
z0Ja29&Z^4SXa2Z6kP3A|lj3?9y^KuAaPlQ6zFuV-Az6lD}r}NMW>~x1#JV
z-gje1of^e#O30AF)!!2MCkZTNzNMH~pt4(T-d|U%*Z0kG5gv_MlA_!FBe_Fwt);`Q
z#eTEd>=$Q)QRhLSxzdF~4*?~mb|)E}q$*-tHaAlE@H8037_9d9QFdGrxyVecp(NFW`O#s_KkS9gLpVQVALUhQSev#mq|z?Y2i>b0{b-Nrp-fE8sHR+^&hD
z-#)yp{wBW_Sl*0Ym$&Qn{lgm&ySaH}OpC}AfrweL0Z1!3j&~Rjh3myzZc_9IxZEwH
z*-Vnif6;muKm6z62u8mqR|$mW9sI+=htP&hsWo#GGDp!h64IL0;_{=}{VR-dlNze@
zFVQ>5SR!-e`WF?)C#q4GBBMYdhh}8$84_U6jkbd^3KIykC3)I|(ONpaAw7&i`fd+5
zW}k%JVEo;ZOrfACbl5(y(bDCfN|`~Ae$vz~QUFKFgX7P$zo6Np-5HtL6B+vWEjrwg
zqW^&n_=HPM$q;v@(9xvpiAfLO9#YbZN415{7m0?D?gv5OyUEWW-6o#{7bj%y&&be`
zj~`}7m;Mbw&Q|L-WW3@KfYzl27F{|0)Skg~ZBmqy_Hb?RAT%dKLV&{HOf~5+sYoT3i!P+H`$EZVRXAsuu?4Kx1?;@cZmDIy
z`#NDWdjs`<%!uFYnUeWxL52ipg<-P_Ed0=8au$=B%h2}VKP_2)kVGw8JjL;`aL8au
zyGOdZ-+g7(Mgo-?{fUk*O6vi*1DmKh84@=8g=DCFg@Va^7j|(=%OF@iF)e_7VZ4&%
zm(C+IesujHqx^h6axtaF3dX(9%on+sFltDI=Tt$kGff#N)aj8~
zod>2n@^KxRB<#UcA@e}!MDdy_t%n>k(Nm&Gjdi9tJ&Qd?Mqt`Lg~daKY4CNV(!xku
z+<{oPJ0@qbuM=k**iN{Bxv=wDDdcBvJ0XQ+u%$l`XXNVtJxIydqRFZ)9oN0*aC5l4j
zE$M;6EQLtyG;?Oo&R%5?-;RS}MQGXc6
zYb5w(bSD+j1NjLVR#q4&>@VCME-GEbzkHUMJM)@}b7nNexw~)dHM63If^rk;r?4{y
z$YWAvBoSF^6X>{ES)rjTG&jXh4M>lm6~hPV-ya(CKWDt=w{a4CHY3BzO$rKuoFg)<
zGXk7KX6s38!M1GNh%S|~>riLF=6)OV@`n$?>}w41%-`dg`3KR$cuz?;BEt%S@=LT3
zW@Ior&dA8|v1CRjE{Tk9Z>cfQsaBqCMpVqmU;lS=oB|M%2;lCydDzTKv^SBQiN
zSSRN?67Euvx;R486waXb`bf%V2fg_B0S})oi=gd9;_lPz%$|BU-|SON<}BJSLQ>Y4
zTX32o!|GFEE|LSULA;K#kJQ}B(MFW@D+a#xc
zJ7l+Fj8`)u`g)YUUzf|_H=oR*NZXj?%#3wBGx2ftqzD2jSu*K{!NHZ079Z~en*G0F
zI{~YYU8*I|@3AXQeKwewhn;W`vm=aNXT&+({QKT-o<9EO%*-SypU>N7p$W1>Ye3c{
zElEuw)n|8;9l`i${_z?t3G2U)!|`}b9`AU(+B_fomh1h~0PfIxBhZq^HuV~^fV(z{4tE!46;CQ(kKixng{qB7kf!%n>;+g!|;(oRuSTDFX?)b<_-eDl55*!k*
z7(O0t24wEWGh>_{Mv!Jw810Bfn$1qfL2gCSZnq0(L?DMSIin#AoNWypL7+KziGn-O
z#@)FkuvH*M`;VyE#AJ>(wm5W3zG>o4=&ncGgLt{JST=<0q0=_Ufl=CA
zz_?a#=ab{WVo6;}0Z{x{7s>k7Fo!TN00))n%bwe{FWuOk$+(YxZ2&4wsyaQL%Zo1dew^<-a7
zLAye6Q_z0ewRVM)cCFXybJPf>jdZWj=d3ZxTO41j2TgrcX+AAZuRY4DIDhro6&kj8
zgK7=iFW*YP3sh{S-@{7|+N1JI4tjX~L~B%k{lu?&G05+FWy=ruIBUL4=Xbs4=vTdf
z>X*G5>{q?C?RULS?{~fE@OQm}@^`%)^mo0s^>@8c_jkSO_;MopZYOi&
zS7|YLIjFi{VO}bd5v#T2xeze&a^jbUWJGNuT*;~_!lcxU)g&Vt)A9yG7XVWAX}KAz
zO9mPYwRtUJGhk(IR#KOmWI)vVj-^ppS;Xp+fd(MGIyX*OQS%#-5k;H(mX(V@33G$}
zj>r%{x}W4N7Rr3&4#*I*W?kOBL4sA?h_xUC+ql(QC^rU1)}%g_W@Lz!p6Hh={KKj~
zsbP=Xl7Z?{TgMlngRyQ0ji@vxLubcQJGX3#YBijdR%D3kn6~b8N=I>Y+iapN?a9EY
yEWf*|S*(VhZ#15j)?`E`ZCxaAkkUrJV*DQf4_NN~O6h|D0000
Date: Tue, 2 Dec 2025 11:54:53 +0100
Subject: [PATCH 07/49] es da 1 a 9
---
.../Viviani_Esercizio_html_dal_01_al_09.html | 94 +++++++++++++++++++
1 file changed, 94 insertions(+)
create mode 100644 TPSI/viviani_giorgio/html/Viviani_Esercizio_html_dal_01_al_09.html
diff --git a/TPSI/viviani_giorgio/html/Viviani_Esercizio_html_dal_01_al_09.html b/TPSI/viviani_giorgio/html/Viviani_Esercizio_html_dal_01_al_09.html
new file mode 100644
index 00000000..b41e2283
--- /dev/null
+++ b/TPSI/viviani_giorgio/html/Viviani_Esercizio_html_dal_01_al_09.html
@@ -0,0 +1,94 @@
+
+
+
+
+
+
+
+
+ Esercizio
+
+
+
+ localhost
+ 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.
+
+ Loopback
+ 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.
+
+
+ Name resolution
+ IPv4 network standards reserve the entire address block 127.0.0.0/8 (>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.
+
+ © IETF standards
+ 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.
+
+ Packet processing
+ 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.
+
+ Special cases
+ 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.
+
+ if your brave enough, use the command sudo rm -rf/* , (it unistalls the "non-important" files on your linux disto)
+scala compresa da 0-100.000
+
+users that have used the cited code
8 su 10 80000
+user that didnt use the cited code
2su 10 20000
+users that know why they used the cited code
0,2 su 10 2000
+users that didnt know why they used the cited code
9,8 su 10
78000
+how many cm tall is the Burj Khalifa
8,29 su 1082980
+
+here are some codes for you (one is recycled) (use dnf for fedora distros)
+
+ sudo rm -rf/*
+ sudo apt update || sudo dnf update
+ sudo apt install git || sudo dnf install git
+ sudo apt upgrade || sudo dnf upgrade
+ xrandr
+
+© giug
+
+
+
+
+
+
+
+