g-#azj&<
zBC#l39sK~l^|k=+=e3?-UfrmNowhQ3`j&`%Yu*%cU=zJU%?rQE?VKF5Vu2ea*uytax1tA(E%^I=Y7~03EVO$8;pQsc_xJic4l#N(H
zmX(u!vQQjVn24i*&+U5zjb!p4m72Ww{#gyALrH&fp*e_*k57V4!
zRs&Bna!pDzpSR+MyFy{dYSN;8$kpM6y;Q}znIK)e2JN}q*xP3P+&p1(b#dcQF5DIE
z1!q55pgX=6yMnpHb%Nj?p^Qs=RPIGhhS&eI{w~~__Ij1tw9FUEDf~Vh!{LHkp}O j6K2ugAOI
zKlgz#222ZTa=eD@bcdGTi7_e`r|(b||3}=pFej@sah$-x3l1FTouT9S*r_Oe?DzkK
zFXTe@8mQ8qXs!0{&wn?Y&F-cJ!ac{9cb;zpAU09BkZJr#17$qCH-DDG&6rs@igmz3
zM&3^7zYr?fZ~NhLAH_THwQ$F4K3@G%)$U@?PQ?Ol4E7taA1!UPECUPK;{7j&l5r
z`-b;-)(_+Q7r>Aw8yfA2ykn+AKgQM?WPXagJy
z&-P>Sap2L@wQMhXXiU#*!WlQ-G~908a2c=;Z{0my;s|{2p6)2(@q%0Pd$gx(yuDr_
zRl;|C;2%xG<=vN{Zeb03(G(Oc`i!$xkL7Sb1$TjL_w1BPV6hqWw2-(BW8)D!%;8c3
z#-46{pA_sbc6aUGU&%N*;UW`29!$a=Mj^JgqE@va3=vsehCMu9evo~ZsS{fAR7$C(
z?$q_hH*y>Cb~ne@D)}x+IAR{@+M5CF-DWsos!+EHzE-+Uxc&P(Z(lR+EHFXFcUZ8V
zeSBo2jZ5JIyKqT{#*!J2@(BmGfOj0De8=nkHbZzsd>?a80oj1e-)T>&%cNUt6j&D!
zYjVLAHMihsoA?#MDlCWlDa~lJ0fvp<^c9r&b+H~)&MMKz$9VE*hBbmL;&O3%_>q0bEM!o*I5fsiPE2$l+^{(<;C;ItZ^G!jn(yO<
zjH+uP+NjrwDrOuJ6Sk;3MR+HmoLb&ARI`xo@Ma$0f(s*Kd`3&1ZGh*ry>h_8{dTzw
z0)FFo@9ym$ZX)Cs$oAC6aSAtrh~tak;kLL4J>tb+kur;E?Sdjm;Bodn)nqpm8mzN|AEiC$ewD-CodsL@GaopNGWFE;}o2lrFKO
zecy*)*)yyn+7q_~GHk|{mYrgE7FvP=CQk^X{&)L*xPO^5#!o#-_XrU3bVmKxMUAewGOl#xQZeK)82y@|jCv2Ft
zRJaXYjLnSr1@%AMC*W=cv#=l$8ZXo0D!ANBX7?W0wlAV3V9|UB*pdu0LAV9nv6~a^
zm{^fL1@|v^bx~*1V{$ib$1)g1v)heN-ji)H;&wvbzBGbOh-_IJUsNmf5#|LPU4`$$
z%@T3PgfAxSvP*TU{s7Rby8;A=>>6MrTU0RuYfUX%EY^i!#~OoX`y5>4>Z=3%j&B;$0S+y;5A6ygusws!$RbMEJtAOdO~LfuJf4O7sqgksUpKK6oLs1tm~Pw8
z-F=Sj`&lV^@@&cOX9BQ+Xd6>(pM^{E7v$ud^zj_zRAAzcaqYfNQ(*gb4s|%O7zotp
zaN(+oH4&?`3XkXEe#%Q=@ys4!5v8{DvzyeIEbdUR3g$5QRUyl2EAKT~Q
zZZB-3QfexcJk6Si$E21wKgYIbN%ts6{Os!pQ?iYUHPPZ46uu8POIY0lD7IFlD{V@E!|rn^-bJRNf8HeM
zB_s>DdJ8+<_em<-Ik?FvBu-$^dIZS(Jxjc?9Axa?`}IwN+tW=I>73{MS!@x|rB3N`
zyCB4SNiEZkslK|3%OLO#c>9&nnsY%iWTZ6aIkXc?g0`vi7vaiQH}*1D+nJ*rkv&Th
z*_U*wX6LnjMYdn(0u%wMeCIqbXk`KD;jPL)Uxb?_9R}R_W|6Zi-~~+xyM9F{p+Ol3
zGT{a00Pqa@9dD{Uf4m4+a~P;}cS-`zPNiE4hIbXbBiiO%;9P&VDaLJtOm*^Uv3t-=
z2d$1qA%9u9IBg6Za{ng#x(C(Sg;}Mzgo?Ctdkt?y3-)7B=0O2>&^6H#o4}Pj{;{vx
zTpD@Q&p6QfJnk4>Qsa{&?T&b#cO0(Q_6sm8ng;KZvxG3k>w=68M(jpat^!wa7}yDw
zLN>IvP?Lh^c^s9K@AV1Kw!h12B$)^yZ^<-qG20lyM=;PBH1Wo=T>-9Qb&sr_xpJbH
zv`{PQh8ijW^o?3NyGOZrMKO@|qQx~TK%YfJ(`bmD<*orR2?i+F{?XM6aOGthZ=t!<
z`a;7z2E`*o{_b#bZAzW_T@u#4w*8kWz<;)pq}$*$8X(bziWnP$29Y(!tu31s;G$((
zOv~d_np7sCEYzeuA7mM(9=n49o;3~qSKZj&Lk3ANwYyjVhs&U=iTC0JhR~YawNL!B
z2Hfo>xsuT9t>@fbx-SunS3wD2?Fsi@qW;$1>HF?(Fj#~~-?uG*uSI>Xcq5M5`#FzQ
z;C{;aAzI-`QN~u#;tImk|S}eT6VzcY#+YC>6i+
zY~9~%)`6>TNxaPmb~k(}A+;i8s|nm{C{(C{-dOet+e#E%uoitM18u6jx;0$6(EFlX
z?e8kxpI$ZDI&eQzb|D=eBXua;8^hAYhPMLMtE2)D^}m4CJ`gY3nPD5ZT1W=^2h<`A
z26tos^1S|-hr8%2a4t0OeUtLXSdSKRMlf}Ef#Idvg`LPOSK8Exc%xLo$dzSLF3Bn|
zwoUH;cvC;-mk0~-CnJxE_AJaY>^EX1%A{Q=UC$Po26x5MrL6=4S!3uw|Mb{kkjSCM
zQ3Qy#ZYr;g;kRXL!KEt+E?s>qSZ~Hqa-TtU8YJUjq?Tk<#SQ321osg{ni|(&6Keki
zax++k)s&lE5_x$@y6QqrGQ0ZDgyc2U@xrBB3lkf19-yHhQ5fdRHZohYcTXZ89zE8B
zOEW}-j$c0fD5fC1U<2FI9noDHE8G>~W?9}3SNmK5U?S4Ay{y?$(`$C+1A;raGA4vQQGAR_3XlV5{Vd@
zEM5p$#H%_Ev+~rYuSvP~e&wErWBX@axXjsQYY7%(IPgs$In01#WVtZ2VV^Acypnpg
z`Rxg`(ISjan0q35V||otyDr?t9)mWiDb2C?S_16}$2pDQttI1t$ks2>^%G>UHSRf7
z_JdZq>%v{`F{sf;T8*+Hc=u#Ikr40Htq`@v!3N@K0oUj{{s^mwB&$fE}0NhNhlK`6%sU|I~7KMe+
z$-dg`nnF=;O2XV#5uG|z7@;_s9DD4N_>ahA)$}0OV+${U6#Lc-wcF;oS
zigrupG|(6?unjEUz=ArmhbCybCZ>XnZa<;5H`||sn@osSD%1|?3^Eqr-80LZ=iE35
z6Px5a#JD=M6w+Nb^2$WA!+884+)OvSOBWL1HA~ry#_9Y5}^`rdQ{xn<^!V)8caIetB@6_r`OAl+-!dyZaTJmNcJif;tc!EBIz=x
zOjs1xNWXPe=>q0b_T~UsfePt1ueZMeS2(DHYxg*l%K$AyICDmu)l}0fs~3iRr*{hm
zc!6rVP^t3!_E+H2KBbpfxr$B+)~nQL<43ynBkWzOd?&or^QB9SIm9B<$Ts^WxJnmT
z!DZOV(%q0AWXv{{Qn+Dai^63w>y+=pBL}S(_K&GI%g!k;%;AY@BMcgw_ENVaO
zc5*fY@^`uErCymdvqkeD#T{yBf#E_KdBwylfLz^cHtP2G;L4p!<6*1N>}rWPVt(lc
z?^^1CUO~NbSf`pMC~~P`4iBfA2iaD+W&4Y8#eR>9M<$)-L-R{{vQrtG2w>CeeKV%s
zB;gv}Oo?aH`yf$3wek*MUOt{&%{~v8pJL0F635gkSZG_y)H^A6&%zDDE)d>slOznx
z1hxwlD?povAmas+<+HcU%a}=K!WC6IPUw8xp938!4Vv&N46VzC@=dWr3wTr-R}uM)#an1YQzue?7e
z)tBJ{yBnJrALadEd2532O;FPSGyJ)Jz3rudE9^ha0S2!LGU4Noer*3UxWH$4OQw(k
zqcD@&KUoGT2c0BDioOF|zKMws7;Tk{qpUu+{~g>w_f6cGI1qnV3-8itO$zev#b9Jy
zw3RYnlnw>vE2dkK?fv-~Yz?@RcC{T#a*VjRv$o+eNO3{&|Mt#cxltX6qLiy7tkH%Q
zD{sJt{Qn<5AtcnT?iQ(MY=Z;IWL&0ZCY;>4>b?>vQ!lN270q=nsE9}|u?Sfti!9+Y
zZ~8OXqPLH@wu#RC>n@g+{sg^_Wo@P6t&z;$#-k}?Rb8k6H_DMIJgJV}5rDzjgS
za8&ER<&{ck7r^Q={;z)b1#p)M_ZB})g!XE3jHBrT8Vp;NDR!QXW|9TIusBfMhq@2X
zwy#^lWp-#!84fqBtwp>-P==rV#@cT(hoXX$Y;&?o{nXF*yBop{!x~-|%{{G!f7lS7
z7iMxua({}ED~D{(tpGSlJ$(AZJHoEuBD%LW-&lgLckNn~qgiht2BA2EP8IkntM5pJ=_wbTrAA-c{h2i_eJFH}RoSC@=wL_5^m(AXGm1$JpC
zGd~vByYfOkCgn9^-T=lnQk`*xqe-aCB@_De)l6vXYD2hB{`qVTT*T##`#vKonUldr51-`2!Si!V5IJpshBR
z+SYJmO@?gW>7Tr|ba&(z*u2(k1R7DmeF8aF}2SJBK@2Lo3BN7G;p!_9$rbk|e#0
zIgrH6;O4?e_P`#di`CcO;d*PpB}1WR;45Bayv)d!yRRbdU<3irfQ^Dbg#LD`>gpJ9
z>A2R2H5t2ouyoHQyycxOd`U7XIz&3xO-b~yQP=PexJ0}JEq*$KT$V9>b;*4f|CLP`
z1{0?9rQ=vv2ZHP94mjT}1?W=Hz@#~GqJlSHIp0Y;k}vR`X#0?dRL6pwi?_)pg_%ir
zTd>}&EW_T*<>{cufIb24#`2-&9(t#Ge{s@D^z8(cm??~?x3;=BD@jFK4#Hox;+-$NxU#3
z%TuxjRJ>x%J4=}M#6i9yVU;2X5CV72w8P~sqV0aR3=`f9xArYX%cW#wy~tAY+S15I
zmp&nT(9-bcP1li~cM%O}d-GFQ2ZrkgHa>*3sA0PnCf-Y7Ixz@|??m|Te+y3e+olx)mUzgAn-TYhxD=w(Z?2IuD~=Cx~W1=TMd-n5yYx4Rs-
zw&{YNwV!nO0=OP;+kzDhuq2aibYJJo1rGpmB-=jRKiYNHy{|&;pv@eFeFa=U2_#kx
zaB8^JujQq$7^u%*miN3n=sf6%q!l>}TLy3W_(k=Q>NI~qv|k7}x&y9w>AD6OM%vZUO>E#0YK-Rkajp<
zHu4+s!r~zoXae7{uHSjRAA{@8JHDBCZO(T^y_)vMz#|ahtDe_<{0X@J9nZJH8_}?n
z6xVC1tzh^j1^XA*$!hDr1UKXkBQjp9UBuX~`2(sYba3N-c;6N62yW1C-!#~Haasn$
zvK74elFzn@u
z_69ed^ES~p1g(@d^rOQ{>**72;jClqgzPZ)`4e5Nb#J;;j_DAm^6On)(eB~$){zf~
z`}>{`12;_;RfqbX4+Xb6;htwtxF_5b?s@ivd%`{8o@aNn%JI*hJ>i~kk9qb#hjy!*
TBq*E*00000NkvXXu0mjfX{AJ1
literal 0
HcmV?d00001
diff --git a/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_10c.html b/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_10c.html
new file mode 100644
index 00000000..03ea3f40
--- /dev/null
+++ b/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_10c.html
@@ -0,0 +1,34 @@
+
+
+
+ Esercizio_HTML_10c
+
+
+
+
+
+ Quick
+ brown fox
+ jumps
+
+
+
+
+ over the
+ lazy
+ dog
+ and
+
+
+ then
+ it
+ fall
+
+
+ prey to a hunter
+
+
+
+
+
+
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_10d.html b/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_10d.html
new file mode 100644
index 00000000..5327ff1b
--- /dev/null
+++ b/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_10d.html
@@ -0,0 +1,39 @@
+
+
+
+ Esercizio_HTML_10a
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ yes
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_10f.html b/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_10f.html
new file mode 100644
index 00000000..89286cdb
--- /dev/null
+++ b/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_10f.html
@@ -0,0 +1,38 @@
+
+
+
+ Esercizio_HTML_10f
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ TABELLA
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_13.html b/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_13.html
index 19c14de9..b770b450 100644
--- a/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_13.html
+++ b/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_13.html
@@ -2,23 +2,23 @@
Esercizio_HTML_12
-
+
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_14.html b/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_14.html
new file mode 100644
index 00000000..600741a0
--- /dev/null
+++ b/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_14.html
@@ -0,0 +1,75 @@
+
+
+
+ Esercizio_HTML_14
+
+
+
+ inserisci i tui dati:
+
+ Nome:
+
+ Cognome:
+
+ inserisci la tua data di nascita:
+
+ che lavoro svolgi?:
+
+ Studente
+
+ Impiegato
+
+ Disoccupato
+ Nazionalità:
+
+
+
+
+
+
+
+
+
+
+ qual'è il tuo colore pereferito?
+
+ quanto sei alto?
+
+ quanti anni hai? da 0 a 110
+
+ inserisci il tuo peso in kg
+
+ inserisci la tua media scolastica
+
+ a che giochi ti piace giocare?:
+
+ Minecraft
+
+ fortnite
+
+ il gioco della vita
+
+ trytohackme
+
+ roblox
+ Peso:
+
+
+ che tipo di scarpe ti piacciono
+ Genere di scarpe che ti piacciono:
+
+ Nike
+ Lumberjack
+ Geox
+ Adidas
+ Skechers
+
+ Recensione sito:
+
+
+ Premi il pulsante e vedi che succede:
+
+
+
+
+
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_15.html b/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_15.html
new file mode 100644
index 00000000..d22db200
--- /dev/null
+++ b/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_15.html
@@ -0,0 +1,71 @@
+
+
+
+ Esercizio_HTML_15
+
+
+
+ inserisci i tuoi dati personali:
+
+ Richieste particolari:
+
+
+ per inviare:
+
+
+
+ per resettare:
+
+
+
+
+
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_16.html b/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_16.html
new file mode 100644
index 00000000..93bc6901
--- /dev/null
+++ b/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_16.html
@@ -0,0 +1,75 @@
+
+
+
+ Esercizio_HTML_16
+
+
+
+
+ Dati Personali
+ Nome:
+
+
+ Cognome:
+
+
+ Genere:
+
+ Maschio
+ Femmina
+ X
+
+
+ Email:
+
+
+ Inserisci la tua password:
+
+
+ inserisci la tua data di nascita:
+
+
+ Nazionalità:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ scrivi il tuo lavoro:
+
+
+ scrivi i tuoi hobby:
+
+
+ scrivi la tua altezza:
+
+
+ Inserisci il tuo Peso:
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_17.html b/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_17.html
new file mode 100644
index 00000000..2965204a
--- /dev/null
+++ b/TPSI/sena_alessandro/html/es_html/sena_esercizio_html_17.html
@@ -0,0 +1,166 @@
+
+
+
+ Esercizio_HTML_17
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 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
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/es_html/sena_htl_10b.html b/TPSI/sena_alessandro/html/es_html/sena_htl_10b.html
new file mode 100644
index 00000000..a0f3a938
--- /dev/null
+++ b/TPSI/sena_alessandro/html/es_html/sena_htl_10b.html
@@ -0,0 +1,63 @@
+
+
+
+ Esercizio_HTML_10b
+
+
+
+
+
+ Servizi ecosistemici
+ Codice
+
+
+
+
+ Servizi di fornitura
+ Coltivazioni
+ F1
+
+
+ Foraggio, pascolo
+ F2
+
+ Specie cacciabili/pesi
+ F3
+
+ Materie prime (legno, fibre..)
+ F4
+
+ Funghi, frutti di bosco, piante commestibili
+ F5
+
+
+ Servizi di regolazione
+ Servizio del carbonio
+ R1
+
+
+
+ regolazione del clima locale/purificazione dell'area
+ R2
+
+
+ Regolazione delle acque (ricarica delle falde)
+ R3
+
+ purificazione dell'acqua
+ R4
+
+
+ purificazione dell'erosione e dissesti geologici (fane, instabilità, versanti)
+ R5
+
+
+ protezione dei dissesti idrologici (piene, inondazioni)
+ R6
+
+
+
+
+
+
+
\ No newline at end of file
From e5156c018ec45105e92a134005bf5f2c82ba90d1 Mon Sep 17 00:00:00 2001
From: Sena-Alessandro
Date: Tue, 3 Feb 2026 11:13:43 +0100
Subject: [PATCH 06/12] esercizio 11 html
---
.../html/es_html/Sena_esercizio_html_11.html | 218 ++++++++++++++++++
1 file changed, 218 insertions(+)
create mode 100644 TPSI/sena_alessandro/html/es_html/Sena_esercizio_html_11.html
diff --git a/TPSI/sena_alessandro/html/es_html/Sena_esercizio_html_11.html b/TPSI/sena_alessandro/html/es_html/Sena_esercizio_html_11.html
new file mode 100644
index 00000000..d9dab412
--- /dev/null
+++ b/TPSI/sena_alessandro/html/es_html/Sena_esercizio_html_11.html
@@ -0,0 +1,218 @@
+
+
+
+ Esercizio_HTML_11
+
+
+
+
+ MENU' RISTORANTE
+
+
+
+ ANTIPASTO
+
+
+
+ Bruschetta bianca
+ € 1,00
+
+
+ Bruschetta al pomodoro
+ € 1,50
+
+
+ Bruschetta al tartufo
+ € 2,00
+
+
+ Prosciutto
+ € 5,00
+
+
+ Italiana
+ € 7,00
+
+
+ Prosciutto e Mozzarella di bufala
+ € 7,50
+
+
+ "Le Cannucceta"
+ € 8,50
+
+
+ Vegetariano
+ € 7,00
+
+
+ Tagliere di formaggi
+ € 7,50
+
+
+
+ Max Tagliere di Formaggi e salumi
+ (per due persone)
+
+ € 18,00
+
+
+ Prosciutto e melone
+ € 7,50
+
+
+
+
+
+ PRIMI PIATTI
+
+
+ Fettuccine al pomodoro
+ € 6,50
+
+
+ Ravioloni in salsa rosa
+ € 7,50
+
+
+ Gnocchi fatti in casa
+ € 7,50
+
+
+ Fettuccine ai funghi porcini
+ € 8,00
+
+
+ Gnocchetti al cinghiale
+ € 7,50
+
+
+ Gnocchi di patate al tartufo
+ € 8,00
+
+
+ Pici al tartufo
+ € 8,00
+
+
+ Fagottini al tartufo
+ € 8,00
+
+
+ Ass. Doppio (ravioli e fettuccine ai funghi porcini)
+ € 1,00
+
+
+ Fettuccine porcini e tartufo
+ € 8,50
+
+
+ SECONDI PIATTI
+
+
+ Caprese (mozzarella di bufala, pomodoro)
+ € 8,00
+
+
+ Salsicce porzione
+ € 7,50
+
+
+ Braciole di maiale
+ € 7,50
+
+
+ Lombata di vitella
+ € 12,00
+
+
+ Bistecca di manzo a porzione
+ € 13,00
+
+
+ Bistecca di manzo a peso
+ l'etto
+ € 3,50
+
+
+ Fiorentina
+ € 20,00
+
+
+ Angus (manzo argentino) porzione
+ € 13,00
+
+
+ Angus a peso
+ l'etto
+ € 4,00
+
+
+ Bisonte canadese porzione
+ € 15,00
+
+
+ Bisonte canadese a peso
+ l'etto
+ € 7,00
+
+
+ Abbacchio scottadito
+ € 12,00
+
+
+ Misto carne
+ € 10,00
+
+
+ Filetto
+ € 14,00
+
+
+ Scamorza
+ € 8,00
+
+
+ Tagliata di Angus con ruchetta e aceto balsamico
+ € 13,00
+
+
+ Taglia di Angus con funghi porcini
+ € 15,00
+
+
+ Bistecca Tomahawk
+ € 27,00
+
+
+ Cotoletta e patate
+ € 7,50
+
+
+ Bistecca Sashi
+ € 28,00
+
+
+ CONTORNI
+
+
+ Insalata
+ € 3,50
+
+
+ Patate
+ € 3,50
+
+
+ Cicoria
+ € 3,50
+
+
+ Ruchetta con pomodori
+ € 3,50
+
+
+
+
+
+
\ No newline at end of file
From d34ceefbbf7a15bf93c137aed6cca60908e0e95a Mon Sep 17 00:00:00 2001
From: Sena-Alessandro
Date: Tue, 24 Mar 2026 17:01:48 +0100
Subject: [PATCH 07/12] esercitaz css
---
Sena_esercizio_css_02.html | 62 ++++++++++++++++++++++++++++++++
Sena_esercizio_css_03.html | 60 +++++++++++++++++++++++++++++++
Sena_esercizio_css_10.html | 61 +++++++++++++++++++++++++++++++
Sena_esercizio_css_11.html | 69 +++++++++++++++++++++++++++++++++++
Sena_esercizio_css_12.html | 71 +++++++++++++++++++++++++++++++++++++
sena_esercizio_css_01.html | 59 ++++++++++++++++++++++++++++++
sena_esercizio_css_03.css | 2 ++
sena_esercizio_css_04.css | 2 ++
sena_esercizio_css_04.html | 61 +++++++++++++++++++++++++++++++
sena_esercizio_css_05.css | 3 ++
sena_esercizio_css_06 .html | 60 +++++++++++++++++++++++++++++++
sena_esercizio_css_06.css | 21 +++++++++++
sena_esercizio_css_07.html | 60 +++++++++++++++++++++++++++++++
sena_esercizio_css_08.css | 36 +++++++++++++++++++
sena_esercizio_css_08html | 60 +++++++++++++++++++++++++++++++
sena_esercizio_css_10.css | 13 +++++++
sena_esercizio_css_11.css | 15 ++++++++
sena_esercizio_css_12.css | 25 +++++++++++++
sena_esercizio_css_13.css | 3 ++
19 files changed, 743 insertions(+)
create mode 100644 Sena_esercizio_css_02.html
create mode 100644 Sena_esercizio_css_03.html
create mode 100644 Sena_esercizio_css_10.html
create mode 100644 Sena_esercizio_css_11.html
create mode 100644 Sena_esercizio_css_12.html
create mode 100644 sena_esercizio_css_01.html
create mode 100644 sena_esercizio_css_03.css
create mode 100644 sena_esercizio_css_04.css
create mode 100644 sena_esercizio_css_04.html
create mode 100644 sena_esercizio_css_05.css
create mode 100644 sena_esercizio_css_06 .html
create mode 100644 sena_esercizio_css_06.css
create mode 100644 sena_esercizio_css_07.html
create mode 100644 sena_esercizio_css_08.css
create mode 100644 sena_esercizio_css_08html
create mode 100644 sena_esercizio_css_10.css
create mode 100644 sena_esercizio_css_11.css
create mode 100644 sena_esercizio_css_12.css
create mode 100644 sena_esercizio_css_13.css
diff --git a/Sena_esercizio_css_02.html b/Sena_esercizio_css_02.html
new file mode 100644
index 00000000..291d5cec
--- /dev/null
+++ b/Sena_esercizio_css_02.html
@@ -0,0 +1,62 @@
+
+
+
+
+
+
+
+
+
+ Es 2
+
+
+ local host
+
+ 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.
+
+
+ Name resolution
+
+ Pv4 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
+
+ Loopback
+ 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.
+
+
+ IETF standards
+
+
+ he 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
+ he 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.
+
+
+
+
+
diff --git a/Sena_esercizio_css_03.html b/Sena_esercizio_css_03.html
new file mode 100644
index 00000000..4fa5acc3
--- /dev/null
+++ b/Sena_esercizio_css_03.html
@@ -0,0 +1,60 @@
+
+
+
+
+
+
+
+
+
+
+ Es 3
+
+ local host
+
+ 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.
+
+
+ Name resolution
+
+ Pv4 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
+
+ Loopback
+ 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.
+
+
+ IETF standards
+
+
+ he 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
+ he 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.
+
+
+
+
+
diff --git a/Sena_esercizio_css_10.html b/Sena_esercizio_css_10.html
new file mode 100644
index 00000000..afdcfbb5
--- /dev/null
+++ b/Sena_esercizio_css_10.html
@@ -0,0 +1,61 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Esercizio 10
+
+
+
+
+ Reti di Calcolatori
+ localhost
+
+
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.
+
+
+ Loopback
+
+
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.
+
+
+ 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
diff --git a/Sena_esercizio_css_11.html b/Sena_esercizio_css_11.html
new file mode 100644
index 00000000..85c03096
--- /dev/null
+++ b/Sena_esercizio_css_11.html
@@ -0,0 +1,69 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Esercizio 11
+
+
+
+
+ Reti di Calcolatori
+ localhost
+
+
+
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.
+
+
+
+ Loopback
+
+
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.
+
+
+ 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
diff --git a/Sena_esercizio_css_12.html b/Sena_esercizio_css_12.html
new file mode 100644
index 00000000..c5fb319a
--- /dev/null
+++ b/Sena_esercizio_css_12.html
@@ -0,0 +1,71 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Esercizio 12
+
+
+
+
+ Reti di Calcolatori
+ localhost
+
+
+
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.
+
+
+
+
+
Loopback
+
+
+
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.
+
+
+ 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
diff --git a/sena_esercizio_css_01.html b/sena_esercizio_css_01.html
new file mode 100644
index 00000000..20f2b778
--- /dev/null
+++ b/sena_esercizio_css_01.html
@@ -0,0 +1,59 @@
+
+
+
+
+
+
+
+
+
+ Es 2
+
+ local host
+
+ 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.
+
+
+ Name resolution
+
+ Pv4 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
+
+ Loopback
+ 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.
+
+
+ IETF standards
+
+
+ he 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
+ he 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.
+
+
+
+
+
diff --git a/sena_esercizio_css_03.css b/sena_esercizio_css_03.css
new file mode 100644
index 00000000..9c896a76
--- /dev/null
+++ b/sena_esercizio_css_03.css
@@ -0,0 +1,2 @@
+h1 {color: green;}
+h2 {color: green;}
\ No newline at end of file
diff --git a/sena_esercizio_css_04.css b/sena_esercizio_css_04.css
new file mode 100644
index 00000000..9c896a76
--- /dev/null
+++ b/sena_esercizio_css_04.css
@@ -0,0 +1,2 @@
+h1 {color: green;}
+h2 {color: green;}
\ No newline at end of file
diff --git a/sena_esercizio_css_04.html b/sena_esercizio_css_04.html
new file mode 100644
index 00000000..5bc1cc73
--- /dev/null
+++ b/sena_esercizio_css_04.html
@@ -0,0 +1,61 @@
+
+
+
+
+
+
+
+
+
+ Es 2
+
+
+
+ local host
+
+ 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.
+
+
+ Name resolution
+
+ Pv4 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
+
+ Loopback
+ 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.
+
+
+ IETF standards
+
+
+ he 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
+ he 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.
+
+
+
+
+
diff --git a/sena_esercizio_css_05.css b/sena_esercizio_css_05.css
new file mode 100644
index 00000000..36580207
--- /dev/null
+++ b/sena_esercizio_css_05.css
@@ -0,0 +1,3 @@
+h1 {color: red;}
+h2 {color: green;}
+p {color: blue;}
\ No newline at end of file
diff --git a/sena_esercizio_css_06 .html b/sena_esercizio_css_06 .html
new file mode 100644
index 00000000..5bcdca6e
--- /dev/null
+++ b/sena_esercizio_css_06 .html
@@ -0,0 +1,60 @@
+
+
+
+ Esercizio_CSS_06
+
+
+
+
+ Local host
+ localhost
+ 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.
+
+ Loopback
+ 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.
+
+ 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
diff --git a/sena_esercizio_css_06.css b/sena_esercizio_css_06.css
new file mode 100644
index 00000000..0f213303
--- /dev/null
+++ b/sena_esercizio_css_06.css
@@ -0,0 +1,21 @@
+
+h1 {
+ color: blue;
+}
+#pr1 {
+ color:red;
+}
+
+
+#pr2 {
+ color: green;
+}
+
+
+#dr3 {
+ color:rgb(226, 72, 0);
+}
+
+#dr1 {
+ color: gray;
+}
\ No newline at end of file
diff --git a/sena_esercizio_css_07.html b/sena_esercizio_css_07.html
new file mode 100644
index 00000000..5bcdca6e
--- /dev/null
+++ b/sena_esercizio_css_07.html
@@ -0,0 +1,60 @@
+
+
+
+ Esercizio_CSS_06
+
+
+
+
+ Local host
+ localhost
+ 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.
+
+ Loopback
+ 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.
+
+ 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
diff --git a/sena_esercizio_css_08.css b/sena_esercizio_css_08.css
new file mode 100644
index 00000000..91fd17df
--- /dev/null
+++ b/sena_esercizio_css_08.css
@@ -0,0 +1,36 @@
+
+h1, h2, h3 {
+ color: red;
+ text-decoration: underline;
+ text-decoration-color: gray;
+}
+
+
+p {
+ color: blue;
+ text-align: left;
+}
+
+/* Stile specifico per il terzo heading h2 */
+h2:nth-of-type(3) {
+ color: green;
+}
+
+
+p:nth-of-type(7) {
+ color: red;
+ text-align: right;
+}
+
+
+hr:nth-of-type(even) {
+ border: none;
+ background-color: black;
+ height: 10px;
+}
+
+hr:nth-of-type(odd) {
+ border: none;
+ background-color: red;
+ height: 3px;
+}
\ No newline at end of file
diff --git a/sena_esercizio_css_08html b/sena_esercizio_css_08html
new file mode 100644
index 00000000..f69fdd93
--- /dev/null
+++ b/sena_esercizio_css_08html
@@ -0,0 +1,60 @@
+
+
+
+ Esercizio_CSS_08
+
+
+
+
+ Local host
+ localhost
+ 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.
+
+ Loopback
+ 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.
+
+ 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
diff --git a/sena_esercizio_css_10.css b/sena_esercizio_css_10.css
new file mode 100644
index 00000000..d9fad753
--- /dev/null
+++ b/sena_esercizio_css_10.css
@@ -0,0 +1,13 @@
+h1 >span {
+ color: blue;
+}
+
+h2 > span{
+ color: red;
+}
+p > span{
+ color:violet;
+}
+div>p>span{
+ color:green;
+}
\ No newline at end of file
diff --git a/sena_esercizio_css_11.css b/sena_esercizio_css_11.css
new file mode 100644
index 00000000..71216553
--- /dev/null
+++ b/sena_esercizio_css_11.css
@@ -0,0 +1,15 @@
+p > mark{
+ color: green;
+}
+p > b{
+ color: yellow;
+ background-color: black;
+}
+div > em{
+ color: red;
+ background-color: yellow;
+}
+div > span{
+ background-color: yellow;
+ color: black;
+}
diff --git a/sena_esercizio_css_12.css b/sena_esercizio_css_12.css
new file mode 100644
index 00000000..f9547553
--- /dev/null
+++ b/sena_esercizio_css_12.css
@@ -0,0 +1,25 @@
+a:link {
+ color: blue;
+}
+a:visited {
+ color: red; background-color: yellow;
+}
+a:hover {
+ color: green;
+}
+
+h1:first-child{
+ text-decoration:underline;
+ color: blue;
+}
+
+
+h2:first-child{
+ color: green;
+}
+
+
+p:first-child{
+ color: red;
+ text-align: left;
+}
\ No newline at end of file
diff --git a/sena_esercizio_css_13.css b/sena_esercizio_css_13.css
new file mode 100644
index 00000000..ef59c3b1
--- /dev/null
+++ b/sena_esercizio_css_13.css
@@ -0,0 +1,3 @@
+td:nth-child(2n){
+ background-color:yellow;
+}
\ No newline at end of file
From a9f76204f00cd0902bed215170d4feb2d4132542 Mon Sep 17 00:00:00 2001
From: Sena-Alessandro
Date: Tue, 31 Mar 2026 16:51:56 +0200
Subject: [PATCH 08/12] css esercizi
---
sena_esercizio_css_14.css | 39 +++++++++++++++++++++++++++++
sena_esercizio_css_14.html | 36 +++++++++++++++++++++++++++
sena_esercizio_css_15.css | 45 ++++++++++++++++++++++++++++++++++
sena_esercizio_css_15.html | 18 ++++++++++++++
sena_esercizio_css_16.css | 50 ++++++++++++++++++++++++++++++++++++++
sena_esercizio_css_16.html | 33 +++++++++++++++++++++++++
6 files changed, 221 insertions(+)
create mode 100644 sena_esercizio_css_14.css
create mode 100644 sena_esercizio_css_14.html
create mode 100644 sena_esercizio_css_15.css
create mode 100644 sena_esercizio_css_15.html
create mode 100644 sena_esercizio_css_16.css
create mode 100644 sena_esercizio_css_16.html
diff --git a/sena_esercizio_css_14.css b/sena_esercizio_css_14.css
new file mode 100644
index 00000000..dbffa377
--- /dev/null
+++ b/sena_esercizio_css_14.css
@@ -0,0 +1,39 @@
+#id1 {
+ background-color: aqua;
+}
+#id3 {
+ background-color: brown;
+}
+
+#id5 {
+ background-color: #BD93BD;
+}
+
+#id7 {
+ background-color: #FABC2A;
+}
+#id6 {
+ background-color: rgb(147, 189, 174);
+}
+#id4{
+ background-color: rgb(147, 38, 255);
+}
+#id2{
+ background-color: rgba(134, 21, 123, 0.75);
+}
+#id8{
+ background-color: rgba(0, 5, 255, 0.89);
+}
+
+#id9{
+ background-color: hsl(120, 78%, 72%);
+}
+#id10{
+ background-color: hsl(0, 0%, 52%);
+}
+#id11{
+ background-color: hsla(0, 100%, 47%, 0.21);
+}
+#id12{
+ background-color: hsla(329, 100%, 69%, 0.43);
+}
\ No newline at end of file
diff --git a/sena_esercizio_css_14.html b/sena_esercizio_css_14.html
new file mode 100644
index 00000000..87ce0956
--- /dev/null
+++ b/sena_esercizio_css_14.html
@@ -0,0 +1,36 @@
+
+
+
+
+
+
+
+
+
+ 0 0
+ 0 1
+ 0 2
+ 0 3
+
+
+ 1 0
+ 1 1
+ 1 2
+ 1 3
+
+
+ 2 0
+ 2 1
+ 2 2
+ 2 3
+
+
+ 3 0
+ 3 1
+ 3 2
+ 3 3
+
+
+
+
+
\ No newline at end of file
diff --git a/sena_esercizio_css_15.css b/sena_esercizio_css_15.css
new file mode 100644
index 00000000..474eb00e
--- /dev/null
+++ b/sena_esercizio_css_15.css
@@ -0,0 +1,45 @@
+.red{
+ background-color: red;
+ width: 400px;
+ height: 200px;
+}
+#violet{
+ background-color: rgb(128, 0, 117);
+ width: 25%;
+ height: 150px;
+}
+#violet1{
+ background-color: rgb(128, 0, 117);
+ width: 50%;
+ height: 150px;
+}
+#violet2{
+ background-color: rgb(128, 0, 117);
+ width: 75%;
+ height: 150px;
+}
+#violet3{
+ background-color: rgb(128, 0, 117);
+ width: 100%;
+ height: 150px;
+}
+#rett{
+ background-color: rgba(#008000, 0.65);
+ width: 221%;
+ height: 221px;
+}
+#rett1{
+ background-color: rgba(0, 128, 0, 0.65);
+ width: 50%;
+ height: 221px;
+}
+#rett2{
+ background-color: rgba(green, 0.65);
+ width: 62.5%;
+ height: 221px;
+}
+#rett3{
+ background-color: rgba(green, 0.65);
+ width: 22.2%;
+ height: 221px;
+}
\ No newline at end of file
diff --git a/sena_esercizio_css_15.html b/sena_esercizio_css_15.html
new file mode 100644
index 00000000..042657e6
--- /dev/null
+++ b/sena_esercizio_css_15.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/sena_esercizio_css_16.css b/sena_esercizio_css_16.css
new file mode 100644
index 00000000..1c683e1e
--- /dev/null
+++ b/sena_esercizio_css_16.css
@@ -0,0 +1,50 @@
+div {
+ margin: 10px;
+ border: 1px solid #000;
+}
+
+
+.rel_ass, .rel_ass2 {
+ width: 300px;
+ height: 200px;
+ background-image: url("../es_html/download.png");
+}
+
+
+.ass_rel1, .ass_rel2 {
+ width: 50%;
+ height: 150px;
+ background-image: url("https://www.shutterstock.com/image-vector/golden-dust-light-png-bokeh-600w-2192855099.jpg");
+}
+
+
+.repeat1, .repeat2 {
+ width: 400px;
+ height: 200px;
+ background-image: url("https://pixabay.com/it/illustrations/banner-png-rosso-2383908/");
+ background-repeat: repeat;
+}
+
+
+.no_repeat1, .no_repeat2 {
+ width: 400px;
+ height: 200px;
+ background-image: url("https://pixabay.com/it/illustrations/banner-png-rosso-2383908/");
+ background-repeat: no-repeat;
+}
+
+
+.repeat_x1, .repeat_x2 {
+ width: 400px;
+ height: 200px;
+ background-image: url("https://pixabay.com/it/illustrations/banner-png-rosso-2383908/");
+ background-repeat: repeat-x;
+}
+
+
+.repeat_y1, .repeat_y1 {
+ width: 400px;
+ height: 200px;
+ background-image: url("https://pixabay.com/it/illustrations/banner-png-rosso-2383908/");
+ background-repeat: repeat-y;
+}
\ No newline at end of file
diff --git a/sena_esercizio_css_16.html b/sena_esercizio_css_16.html
new file mode 100644
index 00000000..29ba707d
--- /dev/null
+++ b/sena_esercizio_css_16.html
@@ -0,0 +1,33 @@
+
+
+
+
+ Esercizio CSS 16
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
From ccc10549d71f097dc691b7d8ca733ef0704ac90b Mon Sep 17 00:00:00 2001
From: Sena-Alessandro
Date: Tue, 14 Apr 2026 17:49:36 +0200
Subject: [PATCH 09/12] esercizio 17 css
---
sena_esercizio_css_17.css | 17 +++++++++++++++++
sena_esercizio_css_17.html | 29 +++++++++++++++++++++++++++++
2 files changed, 46 insertions(+)
create mode 100644 sena_esercizio_css_17.css
create mode 100644 sena_esercizio_css_17.html
diff --git a/sena_esercizio_css_17.css b/sena_esercizio_css_17.css
new file mode 100644
index 00000000..0948b033
--- /dev/null
+++ b/sena_esercizio_css_17.css
@@ -0,0 +1,17 @@
+.galleria {
+ display: flex;
+}
+
+
+.cella {
+ text-align: center;
+}
+
+img {
+ width: 250px;
+}
+
+.descrizione {
+ border-bottom: 5px solid red;
+ padding: 8px;
+}
\ No newline at end of file
diff --git a/sena_esercizio_css_17.html b/sena_esercizio_css_17.html
new file mode 100644
index 00000000..fe2f1472
--- /dev/null
+++ b/sena_esercizio_css_17.html
@@ -0,0 +1,29 @@
+
+
+
+
+
+
+
+
+
+
+
+
annik Sinner in Australia
+
+
+
+
Il servizio di Jannik
+
+
+
+
Vittoria in Coppa Davis
+
+
+
+
Sinner ATP Finals
+
+
+
+
+
\ No newline at end of file
From beabce6d654cd5f4596080601eefc20b3e8b9b8f Mon Sep 17 00:00:00 2001
From: Sena-Alessandro
Date: Wed, 15 Apr 2026 13:45:24 +0200
Subject: [PATCH 10/12] file nuovi
---
TPSI/aviano_riccardo/.gitkeep | 0
TPSI/aviano_riccardo/file.txt | 0
TPSI/costanzo_francesco/.gitkeep | 0
.../css/Sena_esercizio_css_02.html | 0
.../css/Sena_esercizio_css_03.html | 0
.../css/Sena_esercizio_css_10.html | 0
.../css/Sena_esercizio_css_11.html | 0
.../css/Sena_esercizio_css_12.html | 0
.../css/sena_esercizio_css_01.html | 0
.../css/sena_esercizio_css_03.css | 0
.../css/sena_esercizio_css_04.css | 0
.../css/sena_esercizio_css_04.html | 0
.../css/sena_esercizio_css_05.css | 0
.../css/sena_esercizio_css_06 .html | 0
.../css/sena_esercizio_css_06.css | 0
.../css/sena_esercizio_css_07.html | 0
.../css/sena_esercizio_css_08.css | 0
.../css/sena_esercizio_css_08html | 0
.../css/sena_esercizio_css_10.css | 0
.../css/sena_esercizio_css_11.css | 0
.../css/sena_esercizio_css_12.css | 0
.../css/sena_esercizio_css_13.css | 0
.../css/sena_esercizio_css_14.css | 0
.../css/sena_esercizio_css_14.html | 0
.../css/sena_esercizio_css_15.css | 0
.../css/sena_esercizio_css_15.html | 0
.../css/sena_esercizio_css_16.css | 0
.../css/sena_esercizio_css_16.html | 0
.../css/sena_esercizio_css_17.css | 0
.../css/sena_esercizio_css_17.html | 0
.../html/Sena_esercizio_css_02.html | 62 ++++++++++++++++
.../html/Sena_esercizio_css_03.html | 60 ++++++++++++++++
.../html/Sena_esercizio_css_10.html | 61 ++++++++++++++++
.../html/Sena_esercizio_css_11.html | 69 ++++++++++++++++++
.../html/Sena_esercizio_css_12.html | 71 +++++++++++++++++++
TPSI/sena_alessandro/{ => html}/openday.tnx | 0
.../html/sena_esercizio_css_13.css | 3 +
.../html/sena_esercizio_css_14.css | 39 ++++++++++
.../html/sena_esercizio_css_14.html | 36 ++++++++++
.../html/sena_esercizio_css_15.css | 45 ++++++++++++
.../html/sena_esercizio_css_15.html | 18 +++++
.../html/sena_esercizio_css_16.css | 50 +++++++++++++
.../html/sena_esercizio_css_16.html | 33 +++++++++
.../html/sena_esercizio_css_17.css | 17 +++++
.../html/sena_esercizio_css_17.html | 29 ++++++++
45 files changed, 593 insertions(+)
delete mode 100644 TPSI/aviano_riccardo/.gitkeep
delete mode 100644 TPSI/aviano_riccardo/file.txt
delete mode 100644 TPSI/costanzo_francesco/.gitkeep
rename Sena_esercizio_css_02.html => TPSI/sena_alessandro/css/Sena_esercizio_css_02.html (100%)
rename Sena_esercizio_css_03.html => TPSI/sena_alessandro/css/Sena_esercizio_css_03.html (100%)
rename Sena_esercizio_css_10.html => TPSI/sena_alessandro/css/Sena_esercizio_css_10.html (100%)
rename Sena_esercizio_css_11.html => TPSI/sena_alessandro/css/Sena_esercizio_css_11.html (100%)
rename Sena_esercizio_css_12.html => TPSI/sena_alessandro/css/Sena_esercizio_css_12.html (100%)
rename sena_esercizio_css_01.html => TPSI/sena_alessandro/css/sena_esercizio_css_01.html (100%)
rename sena_esercizio_css_03.css => TPSI/sena_alessandro/css/sena_esercizio_css_03.css (100%)
rename sena_esercizio_css_04.css => TPSI/sena_alessandro/css/sena_esercizio_css_04.css (100%)
rename sena_esercizio_css_04.html => TPSI/sena_alessandro/css/sena_esercizio_css_04.html (100%)
rename sena_esercizio_css_05.css => TPSI/sena_alessandro/css/sena_esercizio_css_05.css (100%)
rename sena_esercizio_css_06 .html => TPSI/sena_alessandro/css/sena_esercizio_css_06 .html (100%)
rename sena_esercizio_css_06.css => TPSI/sena_alessandro/css/sena_esercizio_css_06.css (100%)
rename sena_esercizio_css_07.html => TPSI/sena_alessandro/css/sena_esercizio_css_07.html (100%)
rename sena_esercizio_css_08.css => TPSI/sena_alessandro/css/sena_esercizio_css_08.css (100%)
rename sena_esercizio_css_08html => TPSI/sena_alessandro/css/sena_esercizio_css_08html (100%)
rename sena_esercizio_css_10.css => TPSI/sena_alessandro/css/sena_esercizio_css_10.css (100%)
rename sena_esercizio_css_11.css => TPSI/sena_alessandro/css/sena_esercizio_css_11.css (100%)
rename sena_esercizio_css_12.css => TPSI/sena_alessandro/css/sena_esercizio_css_12.css (100%)
rename sena_esercizio_css_13.css => TPSI/sena_alessandro/css/sena_esercizio_css_13.css (100%)
rename sena_esercizio_css_14.css => TPSI/sena_alessandro/css/sena_esercizio_css_14.css (100%)
rename sena_esercizio_css_14.html => TPSI/sena_alessandro/css/sena_esercizio_css_14.html (100%)
rename sena_esercizio_css_15.css => TPSI/sena_alessandro/css/sena_esercizio_css_15.css (100%)
rename sena_esercizio_css_15.html => TPSI/sena_alessandro/css/sena_esercizio_css_15.html (100%)
rename sena_esercizio_css_16.css => TPSI/sena_alessandro/css/sena_esercizio_css_16.css (100%)
rename sena_esercizio_css_16.html => TPSI/sena_alessandro/css/sena_esercizio_css_16.html (100%)
rename sena_esercizio_css_17.css => TPSI/sena_alessandro/css/sena_esercizio_css_17.css (100%)
rename sena_esercizio_css_17.html => TPSI/sena_alessandro/css/sena_esercizio_css_17.html (100%)
create mode 100644 TPSI/sena_alessandro/html/Sena_esercizio_css_02.html
create mode 100644 TPSI/sena_alessandro/html/Sena_esercizio_css_03.html
create mode 100644 TPSI/sena_alessandro/html/Sena_esercizio_css_10.html
create mode 100644 TPSI/sena_alessandro/html/Sena_esercizio_css_11.html
create mode 100644 TPSI/sena_alessandro/html/Sena_esercizio_css_12.html
rename TPSI/sena_alessandro/{ => html}/openday.tnx (100%)
create mode 100644 TPSI/sena_alessandro/html/sena_esercizio_css_13.css
create mode 100644 TPSI/sena_alessandro/html/sena_esercizio_css_14.css
create mode 100644 TPSI/sena_alessandro/html/sena_esercizio_css_14.html
create mode 100644 TPSI/sena_alessandro/html/sena_esercizio_css_15.css
create mode 100644 TPSI/sena_alessandro/html/sena_esercizio_css_15.html
create mode 100644 TPSI/sena_alessandro/html/sena_esercizio_css_16.css
create mode 100644 TPSI/sena_alessandro/html/sena_esercizio_css_16.html
create mode 100644 TPSI/sena_alessandro/html/sena_esercizio_css_17.css
create mode 100644 TPSI/sena_alessandro/html/sena_esercizio_css_17.html
diff --git a/TPSI/aviano_riccardo/.gitkeep b/TPSI/aviano_riccardo/.gitkeep
deleted file mode 100644
index e69de29b..00000000
diff --git a/TPSI/aviano_riccardo/file.txt b/TPSI/aviano_riccardo/file.txt
deleted file mode 100644
index e69de29b..00000000
diff --git a/TPSI/costanzo_francesco/.gitkeep b/TPSI/costanzo_francesco/.gitkeep
deleted file mode 100644
index e69de29b..00000000
diff --git a/Sena_esercizio_css_02.html b/TPSI/sena_alessandro/css/Sena_esercizio_css_02.html
similarity index 100%
rename from Sena_esercizio_css_02.html
rename to TPSI/sena_alessandro/css/Sena_esercizio_css_02.html
diff --git a/Sena_esercizio_css_03.html b/TPSI/sena_alessandro/css/Sena_esercizio_css_03.html
similarity index 100%
rename from Sena_esercizio_css_03.html
rename to TPSI/sena_alessandro/css/Sena_esercizio_css_03.html
diff --git a/Sena_esercizio_css_10.html b/TPSI/sena_alessandro/css/Sena_esercizio_css_10.html
similarity index 100%
rename from Sena_esercizio_css_10.html
rename to TPSI/sena_alessandro/css/Sena_esercizio_css_10.html
diff --git a/Sena_esercizio_css_11.html b/TPSI/sena_alessandro/css/Sena_esercizio_css_11.html
similarity index 100%
rename from Sena_esercizio_css_11.html
rename to TPSI/sena_alessandro/css/Sena_esercizio_css_11.html
diff --git a/Sena_esercizio_css_12.html b/TPSI/sena_alessandro/css/Sena_esercizio_css_12.html
similarity index 100%
rename from Sena_esercizio_css_12.html
rename to TPSI/sena_alessandro/css/Sena_esercizio_css_12.html
diff --git a/sena_esercizio_css_01.html b/TPSI/sena_alessandro/css/sena_esercizio_css_01.html
similarity index 100%
rename from sena_esercizio_css_01.html
rename to TPSI/sena_alessandro/css/sena_esercizio_css_01.html
diff --git a/sena_esercizio_css_03.css b/TPSI/sena_alessandro/css/sena_esercizio_css_03.css
similarity index 100%
rename from sena_esercizio_css_03.css
rename to TPSI/sena_alessandro/css/sena_esercizio_css_03.css
diff --git a/sena_esercizio_css_04.css b/TPSI/sena_alessandro/css/sena_esercizio_css_04.css
similarity index 100%
rename from sena_esercizio_css_04.css
rename to TPSI/sena_alessandro/css/sena_esercizio_css_04.css
diff --git a/sena_esercizio_css_04.html b/TPSI/sena_alessandro/css/sena_esercizio_css_04.html
similarity index 100%
rename from sena_esercizio_css_04.html
rename to TPSI/sena_alessandro/css/sena_esercizio_css_04.html
diff --git a/sena_esercizio_css_05.css b/TPSI/sena_alessandro/css/sena_esercizio_css_05.css
similarity index 100%
rename from sena_esercizio_css_05.css
rename to TPSI/sena_alessandro/css/sena_esercizio_css_05.css
diff --git a/sena_esercizio_css_06 .html b/TPSI/sena_alessandro/css/sena_esercizio_css_06 .html
similarity index 100%
rename from sena_esercizio_css_06 .html
rename to TPSI/sena_alessandro/css/sena_esercizio_css_06 .html
diff --git a/sena_esercizio_css_06.css b/TPSI/sena_alessandro/css/sena_esercizio_css_06.css
similarity index 100%
rename from sena_esercizio_css_06.css
rename to TPSI/sena_alessandro/css/sena_esercizio_css_06.css
diff --git a/sena_esercizio_css_07.html b/TPSI/sena_alessandro/css/sena_esercizio_css_07.html
similarity index 100%
rename from sena_esercizio_css_07.html
rename to TPSI/sena_alessandro/css/sena_esercizio_css_07.html
diff --git a/sena_esercizio_css_08.css b/TPSI/sena_alessandro/css/sena_esercizio_css_08.css
similarity index 100%
rename from sena_esercizio_css_08.css
rename to TPSI/sena_alessandro/css/sena_esercizio_css_08.css
diff --git a/sena_esercizio_css_08html b/TPSI/sena_alessandro/css/sena_esercizio_css_08html
similarity index 100%
rename from sena_esercizio_css_08html
rename to TPSI/sena_alessandro/css/sena_esercizio_css_08html
diff --git a/sena_esercizio_css_10.css b/TPSI/sena_alessandro/css/sena_esercizio_css_10.css
similarity index 100%
rename from sena_esercizio_css_10.css
rename to TPSI/sena_alessandro/css/sena_esercizio_css_10.css
diff --git a/sena_esercizio_css_11.css b/TPSI/sena_alessandro/css/sena_esercizio_css_11.css
similarity index 100%
rename from sena_esercizio_css_11.css
rename to TPSI/sena_alessandro/css/sena_esercizio_css_11.css
diff --git a/sena_esercizio_css_12.css b/TPSI/sena_alessandro/css/sena_esercizio_css_12.css
similarity index 100%
rename from sena_esercizio_css_12.css
rename to TPSI/sena_alessandro/css/sena_esercizio_css_12.css
diff --git a/sena_esercizio_css_13.css b/TPSI/sena_alessandro/css/sena_esercizio_css_13.css
similarity index 100%
rename from sena_esercizio_css_13.css
rename to TPSI/sena_alessandro/css/sena_esercizio_css_13.css
diff --git a/sena_esercizio_css_14.css b/TPSI/sena_alessandro/css/sena_esercizio_css_14.css
similarity index 100%
rename from sena_esercizio_css_14.css
rename to TPSI/sena_alessandro/css/sena_esercizio_css_14.css
diff --git a/sena_esercizio_css_14.html b/TPSI/sena_alessandro/css/sena_esercizio_css_14.html
similarity index 100%
rename from sena_esercizio_css_14.html
rename to TPSI/sena_alessandro/css/sena_esercizio_css_14.html
diff --git a/sena_esercizio_css_15.css b/TPSI/sena_alessandro/css/sena_esercizio_css_15.css
similarity index 100%
rename from sena_esercizio_css_15.css
rename to TPSI/sena_alessandro/css/sena_esercizio_css_15.css
diff --git a/sena_esercizio_css_15.html b/TPSI/sena_alessandro/css/sena_esercizio_css_15.html
similarity index 100%
rename from sena_esercizio_css_15.html
rename to TPSI/sena_alessandro/css/sena_esercizio_css_15.html
diff --git a/sena_esercizio_css_16.css b/TPSI/sena_alessandro/css/sena_esercizio_css_16.css
similarity index 100%
rename from sena_esercizio_css_16.css
rename to TPSI/sena_alessandro/css/sena_esercizio_css_16.css
diff --git a/sena_esercizio_css_16.html b/TPSI/sena_alessandro/css/sena_esercizio_css_16.html
similarity index 100%
rename from sena_esercizio_css_16.html
rename to TPSI/sena_alessandro/css/sena_esercizio_css_16.html
diff --git a/sena_esercizio_css_17.css b/TPSI/sena_alessandro/css/sena_esercizio_css_17.css
similarity index 100%
rename from sena_esercizio_css_17.css
rename to TPSI/sena_alessandro/css/sena_esercizio_css_17.css
diff --git a/sena_esercizio_css_17.html b/TPSI/sena_alessandro/css/sena_esercizio_css_17.html
similarity index 100%
rename from sena_esercizio_css_17.html
rename to TPSI/sena_alessandro/css/sena_esercizio_css_17.html
diff --git a/TPSI/sena_alessandro/html/Sena_esercizio_css_02.html b/TPSI/sena_alessandro/html/Sena_esercizio_css_02.html
new file mode 100644
index 00000000..291d5cec
--- /dev/null
+++ b/TPSI/sena_alessandro/html/Sena_esercizio_css_02.html
@@ -0,0 +1,62 @@
+
+
+
+
+
+
+
+
+
+ Es 2
+
+
+ local host
+
+ 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.
+
+
+ Name resolution
+
+ Pv4 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
+
+ Loopback
+ 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.
+
+
+ IETF standards
+
+
+ he 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
+ he 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.
+
+
+
+
+
diff --git a/TPSI/sena_alessandro/html/Sena_esercizio_css_03.html b/TPSI/sena_alessandro/html/Sena_esercizio_css_03.html
new file mode 100644
index 00000000..4fa5acc3
--- /dev/null
+++ b/TPSI/sena_alessandro/html/Sena_esercizio_css_03.html
@@ -0,0 +1,60 @@
+
+
+
+
+
+
+
+
+
+
+ Es 3
+
+ local host
+
+ 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.
+
+
+ Name resolution
+
+ Pv4 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
+
+ Loopback
+ 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.
+
+
+ IETF standards
+
+
+ he 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
+ he 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.
+
+
+
+
+
diff --git a/TPSI/sena_alessandro/html/Sena_esercizio_css_10.html b/TPSI/sena_alessandro/html/Sena_esercizio_css_10.html
new file mode 100644
index 00000000..afdcfbb5
--- /dev/null
+++ b/TPSI/sena_alessandro/html/Sena_esercizio_css_10.html
@@ -0,0 +1,61 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Esercizio 10
+
+
+
+
+ Reti di Calcolatori
+ localhost
+
+
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.
+
+
+ Loopback
+
+
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.
+
+
+ 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
diff --git a/TPSI/sena_alessandro/html/Sena_esercizio_css_11.html b/TPSI/sena_alessandro/html/Sena_esercizio_css_11.html
new file mode 100644
index 00000000..85c03096
--- /dev/null
+++ b/TPSI/sena_alessandro/html/Sena_esercizio_css_11.html
@@ -0,0 +1,69 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Esercizio 11
+
+
+
+
+ Reti di Calcolatori
+ localhost
+
+
+
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.
+
+
+
+ Loopback
+
+
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.
+
+
+ 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
diff --git a/TPSI/sena_alessandro/html/Sena_esercizio_css_12.html b/TPSI/sena_alessandro/html/Sena_esercizio_css_12.html
new file mode 100644
index 00000000..c5fb319a
--- /dev/null
+++ b/TPSI/sena_alessandro/html/Sena_esercizio_css_12.html
@@ -0,0 +1,71 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Esercizio 12
+
+
+
+
+ Reti di Calcolatori
+ localhost
+
+
+
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.
+
+
+
+
+
Loopback
+
+
+
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.
+
+
+ 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
diff --git a/TPSI/sena_alessandro/openday.tnx b/TPSI/sena_alessandro/html/openday.tnx
similarity index 100%
rename from TPSI/sena_alessandro/openday.tnx
rename to TPSI/sena_alessandro/html/openday.tnx
diff --git a/TPSI/sena_alessandro/html/sena_esercizio_css_13.css b/TPSI/sena_alessandro/html/sena_esercizio_css_13.css
new file mode 100644
index 00000000..ef59c3b1
--- /dev/null
+++ b/TPSI/sena_alessandro/html/sena_esercizio_css_13.css
@@ -0,0 +1,3 @@
+td:nth-child(2n){
+ background-color:yellow;
+}
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/sena_esercizio_css_14.css b/TPSI/sena_alessandro/html/sena_esercizio_css_14.css
new file mode 100644
index 00000000..dbffa377
--- /dev/null
+++ b/TPSI/sena_alessandro/html/sena_esercizio_css_14.css
@@ -0,0 +1,39 @@
+#id1 {
+ background-color: aqua;
+}
+#id3 {
+ background-color: brown;
+}
+
+#id5 {
+ background-color: #BD93BD;
+}
+
+#id7 {
+ background-color: #FABC2A;
+}
+#id6 {
+ background-color: rgb(147, 189, 174);
+}
+#id4{
+ background-color: rgb(147, 38, 255);
+}
+#id2{
+ background-color: rgba(134, 21, 123, 0.75);
+}
+#id8{
+ background-color: rgba(0, 5, 255, 0.89);
+}
+
+#id9{
+ background-color: hsl(120, 78%, 72%);
+}
+#id10{
+ background-color: hsl(0, 0%, 52%);
+}
+#id11{
+ background-color: hsla(0, 100%, 47%, 0.21);
+}
+#id12{
+ background-color: hsla(329, 100%, 69%, 0.43);
+}
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/sena_esercizio_css_14.html b/TPSI/sena_alessandro/html/sena_esercizio_css_14.html
new file mode 100644
index 00000000..87ce0956
--- /dev/null
+++ b/TPSI/sena_alessandro/html/sena_esercizio_css_14.html
@@ -0,0 +1,36 @@
+
+
+
+
+
+
+
+
+
+ 0 0
+ 0 1
+ 0 2
+ 0 3
+
+
+ 1 0
+ 1 1
+ 1 2
+ 1 3
+
+
+ 2 0
+ 2 1
+ 2 2
+ 2 3
+
+
+ 3 0
+ 3 1
+ 3 2
+ 3 3
+
+
+
+
+
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/sena_esercizio_css_15.css b/TPSI/sena_alessandro/html/sena_esercizio_css_15.css
new file mode 100644
index 00000000..474eb00e
--- /dev/null
+++ b/TPSI/sena_alessandro/html/sena_esercizio_css_15.css
@@ -0,0 +1,45 @@
+.red{
+ background-color: red;
+ width: 400px;
+ height: 200px;
+}
+#violet{
+ background-color: rgb(128, 0, 117);
+ width: 25%;
+ height: 150px;
+}
+#violet1{
+ background-color: rgb(128, 0, 117);
+ width: 50%;
+ height: 150px;
+}
+#violet2{
+ background-color: rgb(128, 0, 117);
+ width: 75%;
+ height: 150px;
+}
+#violet3{
+ background-color: rgb(128, 0, 117);
+ width: 100%;
+ height: 150px;
+}
+#rett{
+ background-color: rgba(#008000, 0.65);
+ width: 221%;
+ height: 221px;
+}
+#rett1{
+ background-color: rgba(0, 128, 0, 0.65);
+ width: 50%;
+ height: 221px;
+}
+#rett2{
+ background-color: rgba(green, 0.65);
+ width: 62.5%;
+ height: 221px;
+}
+#rett3{
+ background-color: rgba(green, 0.65);
+ width: 22.2%;
+ height: 221px;
+}
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/sena_esercizio_css_15.html b/TPSI/sena_alessandro/html/sena_esercizio_css_15.html
new file mode 100644
index 00000000..042657e6
--- /dev/null
+++ b/TPSI/sena_alessandro/html/sena_esercizio_css_15.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/sena_esercizio_css_16.css b/TPSI/sena_alessandro/html/sena_esercizio_css_16.css
new file mode 100644
index 00000000..1c683e1e
--- /dev/null
+++ b/TPSI/sena_alessandro/html/sena_esercizio_css_16.css
@@ -0,0 +1,50 @@
+div {
+ margin: 10px;
+ border: 1px solid #000;
+}
+
+
+.rel_ass, .rel_ass2 {
+ width: 300px;
+ height: 200px;
+ background-image: url("../es_html/download.png");
+}
+
+
+.ass_rel1, .ass_rel2 {
+ width: 50%;
+ height: 150px;
+ background-image: url("https://www.shutterstock.com/image-vector/golden-dust-light-png-bokeh-600w-2192855099.jpg");
+}
+
+
+.repeat1, .repeat2 {
+ width: 400px;
+ height: 200px;
+ background-image: url("https://pixabay.com/it/illustrations/banner-png-rosso-2383908/");
+ background-repeat: repeat;
+}
+
+
+.no_repeat1, .no_repeat2 {
+ width: 400px;
+ height: 200px;
+ background-image: url("https://pixabay.com/it/illustrations/banner-png-rosso-2383908/");
+ background-repeat: no-repeat;
+}
+
+
+.repeat_x1, .repeat_x2 {
+ width: 400px;
+ height: 200px;
+ background-image: url("https://pixabay.com/it/illustrations/banner-png-rosso-2383908/");
+ background-repeat: repeat-x;
+}
+
+
+.repeat_y1, .repeat_y1 {
+ width: 400px;
+ height: 200px;
+ background-image: url("https://pixabay.com/it/illustrations/banner-png-rosso-2383908/");
+ background-repeat: repeat-y;
+}
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/sena_esercizio_css_16.html b/TPSI/sena_alessandro/html/sena_esercizio_css_16.html
new file mode 100644
index 00000000..29ba707d
--- /dev/null
+++ b/TPSI/sena_alessandro/html/sena_esercizio_css_16.html
@@ -0,0 +1,33 @@
+
+
+
+
+ Esercizio CSS 16
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/sena_esercizio_css_17.css b/TPSI/sena_alessandro/html/sena_esercizio_css_17.css
new file mode 100644
index 00000000..0948b033
--- /dev/null
+++ b/TPSI/sena_alessandro/html/sena_esercizio_css_17.css
@@ -0,0 +1,17 @@
+.galleria {
+ display: flex;
+}
+
+
+.cella {
+ text-align: center;
+}
+
+img {
+ width: 250px;
+}
+
+.descrizione {
+ border-bottom: 5px solid red;
+ padding: 8px;
+}
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/sena_esercizio_css_17.html b/TPSI/sena_alessandro/html/sena_esercizio_css_17.html
new file mode 100644
index 00000000..fe2f1472
--- /dev/null
+++ b/TPSI/sena_alessandro/html/sena_esercizio_css_17.html
@@ -0,0 +1,29 @@
+
+
+
+
+
+
+
+
+
+
+
+
annik Sinner in Australia
+
+
+
+
Il servizio di Jannik
+
+
+
+
Vittoria in Coppa Davis
+
+
+
+
Sinner ATP Finals
+
+
+
+
+
\ No newline at end of file
From 5ab88e7b257df9c9dd504380feae9eda91190ba3 Mon Sep 17 00:00:00 2001
From: Alessandro
Date: Thu, 7 May 2026 13:18:49 +0200
Subject: [PATCH 11/12] sito_portfolio_work in grogres
---
.../html/sito_protfolio/index.css | 43 +++++++++++
.../html/sito_protfolio/index.html | 68 ++++++------------
.../html/sito_protfolio/png/EC.png | Bin 0 -> 137852 bytes
.../html/sito_protfolio/png/EC_copertina.png | Bin 0 -> 422470 bytes
4 files changed, 65 insertions(+), 46 deletions(-)
create mode 100644 TPSI/sena_alessandro/html/sito_protfolio/index.css
create mode 100644 TPSI/sena_alessandro/html/sito_protfolio/png/EC.png
create mode 100644 TPSI/sena_alessandro/html/sito_protfolio/png/EC_copertina.png
diff --git a/TPSI/sena_alessandro/html/sito_protfolio/index.css b/TPSI/sena_alessandro/html/sito_protfolio/index.css
new file mode 100644
index 00000000..817dea57
--- /dev/null
+++ b/TPSI/sena_alessandro/html/sito_protfolio/index.css
@@ -0,0 +1,43 @@
+
+ body {
+ font-family: Arial, sans-serif 2F4RG5GT;
+ margin: 0;
+ padding: 0;
+ background-color: #f0f0f0; /* Sfondo molto chiaro */
+ text-align: center; /* Centra tutto il testo */
+ }
+ header {
+ background-color: #8A1314; /* Sfondo rosso per l'intestazione */
+ color: white;
+ padding: 20px 0;
+ }
+ h1 {
+ font-size: 3em; /* Titolo principale molto grande */
+ margin: 0;
+ }
+ h2 {
+ color: #8A1314; /* Colore rosso per i sottotitoli */
+ margin-top: 40px;
+ width: 100%;
+ height: 10wbn 0%;
+ }
+ p {
+ font-size: 1.2em; /* Testo un po' più grande */
+ margin: 15px auto;
+ width: 80%; /* Fa in modo che il testo non sia troppo largo */
+ }
+ a {
+ color: #AC1819; /* Colore rosso scuro per i link */
+ font-weight: bold;
+ text-decoration: none; /* Rimuove la linea sotto il link */
+ }
+
+ .foto{
+ padding: 100px;
+ text-align: center;
+ width: 50%;
+ height: 50%;
+ }
+ .centro{
+ text-align: center;
+ }
diff --git a/TPSI/sena_alessandro/html/sito_protfolio/index.html b/TPSI/sena_alessandro/html/sito_protfolio/index.html
index 01693acc..3186623b 100644
--- a/TPSI/sena_alessandro/html/sito_protfolio/index.html
+++ b/TPSI/sena_alessandro/html/sito_protfolio/index.html
@@ -3,40 +3,8 @@
+
sito prot foglio
-
-
@@ -45,24 +13,32 @@ Alessandro Sena
Home |
- Educazione Civica |
- PCTO
+ Educazione Civica
- EDUCAZIONE CIVICA
-
-
- Ma cos'è questa bella materia? Scoprilo QUI
-
- Le mie attività di PCTO
+
+
+
+
+ L'esperienze trattate per EDUCAZIONE CIVICA
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
- Vuoi scoprire le attività che ho svolto durante l'alternanza scuola lavoro?
- Se sei molto curioso e interessato a capire i miei
- PCTO , clicca sul link!
-
\ No newline at end of file
diff --git a/TPSI/sena_alessandro/html/sito_protfolio/png/EC.png b/TPSI/sena_alessandro/html/sito_protfolio/png/EC.png
new file mode 100644
index 0000000000000000000000000000000000000000..54aee3b12813b920455accbf2d86e7d06a82c35c
GIT binary patch
literal 137852
zcmV)5K*_&}P)C0Vj$758qy1=D-)H9%+qYzUYV$df|In}mb}2qd(GmI5TSydi{Qzz!{d
z>CJ#K7}GH&rr8+VxXY3y%a-oF@Bg>4jKvtrF^{mbjOI6t2juHL5Uvpy5tZ>kB|0JMO5
z8vC(&Ra&uXmDcZidvD^ktJi1U-g$j??M@5qZLH6jy_|X)6MWI;x^h*T+px}PaGw3!
zy*sb>q~mk?XAkH0+ROHHZec#n@3<~qD|+60^~&^!gEyszAG$dmu-D48d!a13KT2ca
zf4Xij@xcW!1nyU*-uLJG8#{8Zq6R-E0M)@0!=Y>utT0=rhw+
zb5Z#2%6-x}pEUXP)*ieA&oIa{j*)@;)CnqZ%PEiawLe1lKsB}djH
zNA|Y8SlGVfm&EffU-A~ABzW*t=za#f^*J*&xD;oVU+L&KvwLvDy`hGUf*#5u?3%8;Kvx|
zw1Fmo*i=A7o5;^;?m23cj9_$uZMwjM`5M?7;P((D_00hu2f;ZJAs~SO%gZqNT1-k@
z21+8_6(}!yz9}%wXXo|P%_l^<=7oZQLSw*Ug8J9vl@+gGT7lnI(Q5&}3HL9i`ymBP%FM#GI|Y6_2g?61VQ5(i!~oe~l7>B<-zKHYL9Nda
zOnzwm@b`j@4iqnww^PXRKF^!QH7kxa@Vj1?-!g@g3vYxb8VnjN8#ylxcCJgSbggGW
zi?-6O0|YIWpIsl?hyz0Td(>i@_MLA$w^kd05MQNnNboLflNMupv3wv2MrZ7Ey8qnz
z^%7XxbihK->YVS8-LmmkL}mc)(kojaQwrgp)PWFXU9gw|zHCM4vC`ZYw0EZY#l3p3
zU6?`AAQ`{Em`@RsUGwtyvJ!(OlV5v6u$FNFeiA&qj7BD~wBsIwd1?7H>T3Zq&EXE4
z)}_ZCv2VJ)eqOJ?cM7#)OV^2BR%wD*c6eS+kVUwUl*VmR08J1xKxH9W!exF;9%*@INMnE40
zy0Fl4tk6)pp$imWDXQiHlGn%hADNkb3PWXQ7y-uVK9-QP4PIW(IHy|R(O+6|>?gjn
zc#(*Ixo*z_2x3&g4>NvIjEdD|v^B(n$&94sUA5Yn&)hXrf>exwpXQR3ML8!X=e{tg
zfmL7k&aib00ga$Q`$c2ZJ+UmY93~N-Ee_3eQ!!#21ZKJaMfeN6S3>Zbi|r8>`?c2@
z_!$6A1Hj?VX;}k>_Tv`=#>`mussPXUXir-cE_`Z6HOMvfceD^MwB|Da^sX08>=3}+
zc%L=tgv0ht_dQ^rY}Mi8bUkK`Xnk)1%{RC1Oz-^pmFa6+cG&lBEPi?X5&PM9cI(;K
zihlX-0)kP`02nXXxjUVD(N*cAmt38$)93p@%P4u`H!QySZKA(W9DHrtPJ_4~d;$2O
zY%WO9jpPfvXBKSi6m#eL6%neCyBNBeR=A0liqj5v7i3l;zgR^tSmnUFeewLX_dM!)?a8=4d$r!D_c8x^%~Z}q_e4nnQ5YO
zeOmkvfewTEYg#6?uZN}tW^0~v%v1ND-+ryAMFOCw@EkU^2D1YOd&u%LnqQRFjjKaS
z0&_5H57!xMS6kmx0bmA?8o(N07VFpncx}tKCt^NQ;yi!HuJmpJ*rzVrnsy4nHhA1@2d*aF
z=kELMlb(3we(5FxP+XzAp));cUjO#eGuH_?zbzN&TYq+C`uf#7(rSHw{icm+L7+OX
zSkX8j3(o?ffdIcWEHp7{k2Ic@04P?c;)YlXz2k;M7Pst!3E8FA*g$z2t(eq&S`-_%
zYE4;{g~hYx6;nrP_*J^%8|)o_)XJgpUY3pK>Lwm9g=Y~3wMR}x9}(KL+;W%#3y>W!
z07Qn{5L_|rxam+n?=yhvn$G*|AsM*h*iU_T@ggncvcZpqa?6Ss7;X`>wiH7Nt#Yv?
z=rWcx&FN)p`^K=@g+rnRS}}}?h6^K1Wyv%)a51}^a7|%Vw&uBq_GvT;h4vL%zh7O}
zvSUz1(7;T%TSVjtf@1B}d$T7eRg?)AXyygTW3siy4J44(YWEI(_GZLUmS1bdn*f;s
z36S0<;J}6XfCD$C-#&bEI&|%7v-AL~EHIJ*+*OMIeMlDD2QJ={F28=>T$fmO03I*g
zn7p=0paGJPJY;iv%we0;z6u{)qi4jui1z`2ygn_L>B$#dnJ&~iZIn=-lht;NeWwes`p!TQOL0QURf5){6h9M?8dpwynZS)$kEc?&OaZbr_Wujn
z(dXV3y_#3SK?A@yx2`^4*l}%6tc$t(e*G$bwCObuskw$hf2MFNoU@=cpO@U`vSrPo
zk{v-0JPQlZ08lr_qfo**dwPLd3T`Nm4O*U&5K4qXoQN~8*v#^U`aR~
z4`asIz_HI6xA?x92E>YEk-dZ!SX_A!)^Z5m1tvGKd6F0cBVjQ)y)MhL95=slpR*5@
z6`ci0ho)QuW`L$MT$VdMla7j(>H~9^VX@Zi@g6s<8M+pFBzcHlOsnPhD(+<9cfGs9
zM`)h0EK8IrpZ~Ob(gr=I2k>E)@w)52>(dkEt~`Fj8pZk)pF=TnWgQUX@6(mEa*E=0
zKUGX_AI*);+;}?x(BhD_d)R1oxaBwQ5q&?89EjrmsbqDg`~3eSl`NMnjkqJ<
zsqSUJb|t(F)0{^xax9=_p($k+ccTj)%eEwQak=FbeOHhrat6q*Nm&tkK`;x-ikp^6
z^V;Xdx7f+rwF1|@mDEGB0f{{Y{U#Xc3@)vJ#28v2LJVe9*+uM4BgW|S8^jVuj4cFA
zFhzA~mtwZ$J+yDuFccIgOoSfZ0-Fa4l(bvcH+v6)f=91e?7iKxMeu!ByI!CC*zDrG
zPQnv+<;^y%O-~l+-BI9&^;VKubnRNv0ao4D70)|aalLQKO}SQouO*2E67u``5;m-~
zm?9vzQ_s3iD0%07*QF;51aG!sZ+mZ-F5+|Ug*z3?^M{HDzD1=GXI{S5z?CuNXJyy9
z&Bxv7ZN(&i)M2eT5CL|^M^|e#pkY2(Dx{bHGUnDb&XAy@
z46}CSsxUwnXrOdh_ForMgm&cj>^uH?{X!WEqKyp>E59CY7KcsE(Z)-5uq^0B#Y;^a
zmw>Wz0}(&Ma6#_Eh}VvFSyw{d$}89x+_`Rw^`X52dTh0W1un_mqG{ZZhwZ&OJwas)
zlrK<^hXv@yu0jV%$t)|=kFMF7-gV)X>2p`)1Sl*(V8Rk>0galOt3_&9nE;#(SkIM3
zM?%`eRVVm3J^Mh#7O@P2pWx2Dbz`nS*UzAAd
z0+|P~GbUm`Wnud7CL`G1X~EAXdYw(*P2N136zM^-w>P#&VZ^cY{aNLlLjnP$AbA79BQ
z%l^08X(=pDW2OvKzdAptT^-5GEg2o-7-IP~i`)wnvd|g`Zh{D;4_$yVsYh-I6LX<7O2cduU0Hxhw9+BFS8En+&2C(lU~ht$;KC5te8tkwD_3lp
z?kwi*KwA_bvkdf5WR&jUcOthF)x+%
z^`48bN*}&ttFk^9WYxHB
zy}j_-em5IFTT#8n+_H%HUXg)4EiJoV^aCv$Z#W%Ka-W7b12?XhCE;$y?Y!(P_SOc~
za=th4)rJ#u^n3Q5XG77#Xwtfcx4~os$`*CoBo{hQ4Z{ky*m6EBAxjDZ^2PSwUyLui
zJ)4$a_+97rQOSZ9Iu|`ki*+F~3ILs~jKE9?sSb(nndQfTGu8Fsg>uc3=S>KJ^}~8^
z5mEjUL`t{yv#6inEYk(S)sLBt3}0EBzWgub#{4G1P&>pmNkExo+c7OMf|
zjJeVLy~~JxXFS>J_k!6WF@yG=)J#CR3YoOHdB!q$1*nmUi@OZvt+>-V)}sM7no?BC
zZMT@piuAw(a*_HC*X?DXMh0fQ02}K1KCEPx_bQo%a)eyCp52lS(3_ClPcY3N^p|@5IA!QHzv(gBQ8!EF@fcKN_*QuQ1s`MGf9Qh3QsJTMNSfCAlae=W!
z$!igceeRZD+wC-x#%m>L46TmK#2wDE150L_dkm8q#Y+&bj$yQ=_f07!fr}6c9d)Jv
zz}Prqx_CvXWj6PxT)9}~zY4{>x#rEC?+u_K!{EJ$YwCC7Tj-Cl74_8SMHH5hr5kdy
zW79J&<~2w0*^T^h<++RyEb0P3h&YJdGP)E)n#BE7v=r0+6=8_dBt9Z*?|+J(#aX+35HKMFvcUhKPG=E6Nq
z@$#grw&K+Um<)V?8Aa)L-n=gTw&HrX-nh3FtrORa<~{3(OX$7N%gso=-Vd+2PA<7!RgZKm(X|Y+c=&Ig~~16?Bi!D2(^PGF6|1ATF!Kbnm%4fHqR7D~7!tY!S-2STu%7Ff^{M5b$z``{
zdMSqE)_xYB*Onhk5*{6XA2m;-F#{b-P9kh$%IC+yL}A_D$IZ7X4M9I
zVSmod#M0C=NhY$4O@Sj!uD^2)S!Ln&cyJN;v|F>*XvBMTuMnam_PnM!v;Js1XT`dr
zTjEFl{LEAy*Q=~5GBznv$I`pc{yEEXM95@y00Yt4sNuS_x+WwepE;mP~sLA1pZMw@$C0
zfo3it!;6HRM>$}9>U!f?n~^|j!^obgImM~x)N9xJJcj`m02v)5mfrUyVItCDuAl^?7d&>5l8I%gSd|V~4Ae8b0F-qg9tf`V!5utsYBBR`X)yI$L#G8meidPR5DO
zGPh6$Dh2X)Q3k5DQ)_jJ*&w&k&y)ytvRt8`)%dXzanTMkP{ZTnnRV094#FPeNA7AX
zCMSW3db(JgUjn~QGwe~{2?b%L6dF_dn4`~&o~kH#5yz`(zm{P|AOoPZ5z~h`W0QEe
ztJFQ#26;Ru-owj7BFKW*brvgmpxq6O=3=3amRBvu%;d}H;8$aYDGNQ?OX9iG;$~N+
z);J$n(R5>p_e%dL@z?q$oLm)F(i>GtkPNRRNpmeSbyqZ
zGp9mvI@D9^Ng_>HPEa^WBme*jB#%`~vV#SH;XVv-1PHHGVfqJuu|@x`PFLu6EGH~J
z${aEsBJ?w8L{=W|n>t*O1tabolz`k4Z!Dm9Y)An?x7c_lHf_`%-cK<~GE#4}POeZ{
zvSfRPD-^4hGKjCL41=uDbGGfYzt`Z|f$vaQobM;*uh9I7Nh#R?nL#p!_3L%|UM?9f
z=liwNQ3KP+dsdbo@og-LXux3KgZ`08(agC+CWP<~0K}VNT~wf-y1m@E$)V`7mk}3Z
z|9N)A#^TvwVYl6og^_SDaxR<>4_F6&hK=8j5ujPGb(QSM@Oj9%ASC)nkI
zx|TU)jNvLRiA_`<(6S90ulg@9wfr(wWUT@4lu$KyV`%vlbYt?{7-k{Tx_7(?Fu<3l
zuZ$rQXK+Ksqr1l7Lf`g2v>u<=B;ziNNdC6FUC|^g#n@s{zS9_-7jrTGnjGMjoa^s;zTUd7b67n
z*!`;+-YpPZP1cCO8U_bYBWC8&
zh!P)O3cW|YpD1OAA5UBcR$2!f?=wgQwvt;476Hi*tHmec(
zAd_BkVQN@&GKLAO(F3c2#Y-Ntrw7+(OCFmdquY7e8M4!qt*R(KT=XlXs8~)0vZD$O
zOt?yocqcAQ>h-J<2*U{QV~*{4R_kjk(25mK8U`{+%;{XuusWF`vEPX5g)tru`@`W!QTlnfR6+U
zcl|c}_2US(9*+Zr?KK&JWM&$(3@*yu)N^S7uf7UKZLza=ZC63Bbsu$6ZTYpv)z+w&
z{VeE>MQJm%z3&?8I6$q0j;$j+rFFSZLSUyp!$k<_-NB300lp|1h$8i~wJ
z&?0MO%AKqvOU0)R*RLuYvDz<_W3Cua!e5#6L)96?l+5*JC&v)JkOEu9TDyR(?L}&g
zp|@LO5E8Hi5at(Ns0b_g9E}{b2iD~ZkPLcr05lm-)+h;UrqH`bEfe*0Y#aa$_z6^L
zFt9++V6R6EUToh#6zkfnG2H+L-!etR`97Mk+nK8}IBcofF~4wAS#xUA*J&+;Z<=CZ
zX8;H4rkOnHNNeHM7GwcfnD>l>xP%>dq!S|0w1S|6kUKRA#}o(@Fo-%bCy*Lcy6G;z
zo8yhyd^fF_jikS2VwJjF5;$i6UsomfCNf_M1(Yhb?iJPyByvj3sEH
zw&1FX+g4|jzH>Qh=80QbT+fQs=hG3gMxLM^ocB{NPCB8KB6VG}TDK%)lg!O`D1-C!
zS6*Z8#EtuHRI&BSv`Z<|`HaQ<>?MjxMM%Z<8Qn$r0!8;EY;pEpUkkls9SS`=2%Bh*
zG4Z==y{iSjJ0&2A|J`GwI?^1pJ{_x;X(aG)cHjy!>hu}K`Xut4qfRvc=?$}sD>Rnd
z?_1`LZh~T1DQ?AGq>C)IpO~M!^_JW8dLr>sDLxH8=Y4mrS<*_JRXOhFF7Qm0)@vT}
z$M-02!D!Ivk~O^*RhJ!g(%nENS001_KSo2j8J;t@rmWkRcTfuD%-TQ3nWwQ9!CxVZ
z{rxijVc>|I^<+59KBrDxnU*E{+!S+X-@@zpt_FbN*)XE+=@l8Ve>wA0UYJcXG{nv3
z_Vg}a-QWj};O^vbMN-uX>V~%K56b&Ig?12{K_xuO=2wf6+lP5;BEEy*phHWvz6z%7
z8iQ|sNd!RvS?3TTKL6+@VtoTMtuC2MFb^9kKw8O3-}sCDH1bY@8^=Jlna&%vK&u#)
z7?EW<0rY;Fb3?$km4rUeoc5XqVaBG9_O(y@sA1oWptW@hvX)NTf08F6v8J{6p;?>d
zYowlmfVkd9#r+maCtO;bq{c4$#_am1B<+DR24@5`N?0%wQb;z&y{t}_yb>jdN2g-rR
zCIr!#(U{oE8b`e!_22fP4TdezPmV1kX9G*o%a5=KaRc)F+j-XMv6>A%PhnS4ecSetGy9yDgY`%U#aisJ#kBlAhm1Z2@SBVVZ`%w
zz17nocO#&r4fvZ#1^!B&hGSbkPI^ZQ2n%8Ezz^}z5Qh=Z#4}equn)W6Ci8c>n}?d?v!lP
zc0cc_<^@gaZ?{h6%VT{zX+oQCX{^~v7d#uy-Qdoo>sEt
zo~DPI4)C&>i#KQ3qm*@8e&I4RL01WwsjWR2r4~^94&cy$na`~0_0kRn_8tD&>G0D2
zy+L)U*%%ft@n@Cs6U2piy$gM4-Q3^01sKy40UeN;2?8`GWeZwRx#cgP1sFA$$2Th1
zrYYuP0#idHcl9FmTd7E$(-lZwaYfd;od7DIzv3Fz>s_UO
zoKd8n3&4wfFxNY6*0dL1Vl&a+w-~&RIb}Y}OFQfpG-63oo+fWXgd_(89KPJp1bysH
zmr*>1S?^?h^z1wAw>~{hS)n&o{F81ryKr=1VQS2DL}QJuPt
zaXkuHWwn)X7U3H*){!mIZ3g-1*EdMfl{i}`c@S**07_RfJNY2!z5Xr=$KIS&FHb<<
zZcQ^<6J2TPS>tXRl!D|3t
zjJ+1>)Vpn$6?0Q%Zqfkyo>8QZW#a}|6sdnxMe3Zmz{v|(c}1vuVna5#@_Jj=Cc?rj
z{~jeSLBGy$wc$3wtclkBx9ZHJ%v0A2)B*U5&5H!GPy6ud2ZP5qED@`)@X|4@`GpPZc
z+M4CsV0hhX$r#U&h6(L`3L2PJ_DwT~NxoAQsj&WI-nG@{dtN*N`rFD6Q0P4iH$t~d
z6kFtv{*{wgLROD!a~aP>{&G`Fu>f5^gctgqHUX+_FpS(A=iee%po1V)*6i3%sJEvG
zgY@k^;+BX3@DqYGEkHFFu6+=Li^ikv#qYKjm0e}U!=7|v)Y4=;d#gi}2}>ppgd{aN
zy8aLIVJ{g2Pn%K^7)97cn1@Ck8CkY|{5M4TXebK#2_f|I(sX~X@w^&!GRNnhow!N7
zDKdA#<;-4raHf`p&Vf52@?BF|A3{E{A8QR46>O+2=hleQ+OF$4h*aJL24LvlMxk?Z*
zrL>#hyJT40CwQ*Y3lV#yxg!g(+}efWMRc^+r|fUu#oQ)yb#*Xqzdao`-v)nF;NP{T
zLzRSMKKY%+i)n1#wtkkoGlS7(210|TvjOHaE)W8*5x;X{97f)I>d~wYkshAzE4My^Ef;b7)@`9O$~r0QVC$p*qlX_c8r*4a
zbw*(-KokNol3B1`C_?`YFH%25Md~ED)X6LeX--dnzlzjPliow>BymEzKJ&iElVi
zcdg^dwT)+Z2nc1=GVgsob0}tvObl7bVb$bL&&K-bZn!^mcyc{
z`r`Ehv=MV|yGI&^R15Gj^}9aZG4EKffY`2i4y;s}<)gl^ZKUfyvP8VYRrCV*78w=UN1@u$pTrVMEUgt>pi}qZ2?G
zMADxxVy;H>^bOTN+_t!HEsWOxR^`eS$A0lgix*wFHCul68e>gO_z)Yk{v#vI`ayce
zkGUm0$t7Ec+1)WpsMtot_>6ga_8@dZFP&9LqQHg6VXxM9$>D066*N9ys%;g}g0T^_
zWNsQq>0fTeG0@Vc&|31>^K(lrq7;mLXs3w6!K}HqgUwrV?p++S;?|Z~=8;bC0r7DH
zKktvPCIo4xf#e3jLoJgKf>6Ytm*ft
z-|5w|sIkJ0CY?5iu3hXqqf~2*
zl2E{eoB$fM>w3#AD935VLQk@T)wK@lL3aaY$)GS109MLFafxfJ9Aa&mwX=Bf33Db>8BImv2d{
zeKBXH;nWYxL?!;Ul<{o(TA{dG1vA>JvD{(>z{t`;xjeh-
zQ-~}_`?bU`Gk2%wq#|H^jZidl0?|UcrCgv-kt_5L%AU2XS!h_F$MH!3-p|!C>g^X?
zl|Fs>R$Ip$Hckhc^c_ANr>_OLkiV9x(R$;$r`nPy_SrJ)>hhU-ZuuJJNqyO2@MwS0R8ur2xW&)TEa!PAUH{VGeznuP=B~i
zQ|I@tBK2RWP1n0+fqX=niMzz88(zcoZ|
zF4VRxT&zIo3%4|0lo0OAczDwaWIgf$x;qfi`uPAU9Gn_Ka*Vk`*)srGKi6mgbc!K+
z_APRSen-|eO2_a%sCl4n3}x4ql}hM|0HOcH@>`@mS^$qp;|y}e;$VqfO9*Ic2s~et
zaj-RzRRVXi$|dN{^~qteR@<9LJiURCkL|G%s!bbxRLG0LX#;s1$5?@Gk=Z(+(9^|*
zJO<<{c?|TCHLuvX8ILEHLKD>MSvM*++|TK>!uVwx4`YT9vei6=Rnrp;hv?MOM?RTq
zTP=ru=eVz&w|KDv*mGDRrv2LLk6)Dut_aN+i$!X6!KRyHoP0;AFLcx|*jmmo;9BB_5=2Na&W
za1Aw8XstO0U{j0MbfzKMLg)8GV=63|*I|if9^V*76P4wc-P;jE^fC=;qs1rRbr07F
zZEqq`!9bjXZ0gNcC<8H{q>j+7Pf}+l2-xis#2-m@o8)uoaMG*Wn0oo`BBx$faTV*`@`4JCOkvxCc!D4MXqAN7V+woCr>PxU7Vn
zsM9YVAteM?@(vzLW-@VnT|@RP$ul3nWUJLrUdn!u?BI%w33dncI#v_UbmCkhgZc>a
zfW%sQW#08y54jfOFdkC8b3qy5b(xKAhbd8om6{9Ows4F9oyYSQW}5V*E?U6N$#Ty1
zZ@Hymyb6z2&sxH_JTDYSDMN&E%o>}4>(kZ(MXRo{#u6se9;JQ{7)y=C4BCf}Nj&pL
z@pjgq9|l}#s0aPmG-h$p8-L~e#fznx&vCSltdWsv>|H|BH@gpk6$=TUtr)^KJZkkO
z=h4Z(5gKD<tf>lCe+mT`>L
znJ8=411IRhR$6d*BZ0}OYWz1`naXl-pnMqP_Fea&%Sz@Bgk#4(h7b;mKTGZLW38^p
z_qS1JcfJ0={fq)~tP+fVN3PI&=m1?}t~*#iVzeskLhj-UC5!wN0pLdkgzP84$S|-N
zGafh;unv7jRA&Z6iy_*ztw%sv
z7I5uNElglbHdr$gejV#IYTWtWInHNUURCYaAhSv%@}sEGlrl5egQi-NQC~7)ftwdM
z5g1cCM`U+v(Y~ua4tfZA#_E#DvP1W}`95nc(cq^{qs;j-@Y4Y}1QQvXJ~
zNWBPswu}9e@=A9J0MRvYYicZu)Ov=J3SYb6XTCc5hGo8?EcOthONQc--hMb>6gsPD
zsBIn8&!2R9dAQjlP-HE8Lem4iaW`d!KJDm((lN5iw@HcKCBc$=f#M3yF<5ITptA$d
z-a_J$pB|V;GIbAhCDFNjzgOcLTv+KYhh}$GX^&9nM(yg^H3Srg;y-H9=kvg?`hs(|M=)*Rv{kfS{teLxHz%!
z-le$S=TxMQ71AhDukIUTEDYvxBul5aCd|4saV1=KxLJ*?XRjD!$!V%`!`0krwN1PM
z9bX9kt@c0bJjcBP&Z^@;cxb#`Cgs^tM7&ly;0dGyF38i4PR;&b%Ib?FH@
zJMiA?<#N`i)LqtHVyLmCari0f67x~*BV`ioeY8mn-Mh$;F1oCgQ>=D6kL1ihlE-E{
zN9JJij=C~y2`1|-5{&BX&MW?l=Il_YIHXnRljjgSq;GG~uVJ!`HA!RLEtK3mZ
zjodwBn{_c)B;(;^3S=*Uha5JSbC!X9X{v2`HTD)+58!kdFe5GBVX|bH*MetIRze(}
zJO~5(0Z+sjvciu+;w3-c=Xq?OR_FWtcvpBOJM8$la;k&-m^&@MN^rzMmC@+bgjr}F
zn8ujvRiZ<7^AWX)V9ds3Wi&lk2o
z=jA?l%=f#V*{~S&eJnkek!(Q((2C^OSh#9
zw(dyl#O&0h+M%*8P)4ms76|+|5d7_gr?wE7=`y)M3Za#SHOXEbr*F^b!Er+OoF`!6
z2E*E&RsB~jWbJne`&F`#u9JJ2vjgw4ey?=WzH8IXb%r1Sh=p#7iatZh#uEJQwrj0G
z{%n<_GbmNlGd1NaE{-zrI+P|6{%|-NnYWk1x`}G
zy=uoefuXBN{mV*bId#j<^qpOcX`ODcRzh=^Tpdv(8j8-c_I$D#Pj+=f>-3ToPB&)`
zWXw%joI7+7)$>r=NPmYetS2cJ!wmSbUhDYXVyC#Iq|K1%wM7X;YXr8BR7U7yba3#2
z;w8#eGH7I1=sK>|@1Ip!%G(sX{h9I(NRj~vaY7pahC8D@VHf`Lcj84G@rBy*LtaO{sx<-8vjH&@_Sz@)
zR5HfaA$vTtI~eQF4X>exCC8fjmrHM3zTXS{+S;p#Zc())^H-z2W>eG(AgS#la61Nx
zm$RltgLe0knf@Y30HaGIyBVke6m(q7!ob32LLwQ5P82GJcF8h
zkIs3ca%=cke?~W6t}{Fr0mgZY$N>FK^XnsYa{Lpeyc-XFoWEt){t%~l?6Fd+6)k~*qf|2r;RncdYI>x-j^mnG4MI2|6B^q{Zn-S4Mts%1Ji`LKS
z>5o1%7pZR&)72*~;QquFc9Bx!-*e%X^pQ)iu1;LYg~7Z?ZZK`yYZt8;TAx`r8t3~Z
z8t$Z%t7xE(9Tr(U2|b&DXAL|~gVGp>A_u?pP@;NIp%%mury6o%dD*X?^9lM300hjh
zk#e}(8!9BcKv8>DcwfI@=4pS9mWBVjDvh{>EdH`t`h~5H{pYwO3gqb-T7uYJlV{C%
zE_GkEMFkziKQaONH>+1@Xru1OcsQ+w+E#?Qx1Q_z3iYeacxUCcYVFCiGQ*zhN`~z>
zz-A5O74Kr4Zgttz!ebY7IjeQ6?$gK$hi?H~uNe%`9nZf5kHC`Heji>6{$?$DfgePQ
z+a%7%;%~H9y8YLMj(+1M=KL%d(iFQ4wziS9EAxJoY+~IAc_Lu&h0A?1-Q{WO8Fe9~
z`Q~1ep~dw9*U(I?_D>qEb$%hca2f!NO+$%OQH&{#RnaAV7j+JZNs809P8p!tL}q6#_~tmq37zI_ur52ryCUes
z4t&+5c&;}eC^vAqMWWZG8r!Gj(&r%Mb((WDS|66EHIW=^kJ!O4ay2XiHAn&3MrN)7
zp%QH9nnDRsm0;6v0eW23Ff8_wj75p{^`pkH_nT0^Yr^!mlP{Z
zcSkc!ugp0t4{PW;Y=bHwwbRHYh#Fa6F#J+EF>lsbALtZ8;QrFrL$Ge+~)SsXt^_#0mofUr|P+VmfWm9{-@*CFZTSy+OK<+MWIXuPIkR
zTk&ok4*YxHzChWs3kHBi!5Sy{CwXKAe&k75Ig*q`+ka#kiD#5rP%;&bqW6UBvteBL
z$vUDZI~_twJbYU#(UVMZqH6<$C$apBpo_-Gexyu^O3!k`M$HEPbxCADYKzEHyK`6g
zskEhV8?jORPEekdSXo+$pFZ~mWqi?daHyaSkRc9$wT!|*KhMzmozN#4qpd$j{*Z*j
zv~d|sQP?}MI$fcu6_*LXu~-8d3;U3Z)E7)R-fV-4)CGDRHv}T?z!lAybs;f5VtZe|
zdPjPP;(FiI&n4M@rfXzT;Lc|Ir3PChF&T`U4oy?vuFSZJn8Il(esJI1y$SG)4F@8DVWRs?I1#L>m8!kV{Z%zyciCs*lGn{>xMvbf2qiq2tHl$ayZeo;
z+4ZiP&q8vK8Ec=eTjs>>bHAdI40&judrY{tBQKBfjD2nvG`K!bQ=IeBXa7_dpeKg)
zrL9TE?Q|HHd7S%~JvHK8$+uY_^VT)I;9nkUZ4i|x)ogR=s_~v!gBVaPRFzeFC6MVrL=Dh6w%w?r7?CQ@~=u^6Mc4St&~~=TJ>q
zfZPk$!bI**CtTCKC5%ax&!;JG%Y-|Li=vvNts4yI0xV*w=1z{i&68}nX}ds=_Eyy9
z9Vv_8F{;(0X3zRQqFw3VycDHXx&{{~ah-Q6uJ?Iae4|=kwfDYj-+Te`Y266)$c&qo
zc`EIcb0O;F5msjSopLz1iXEI<5C!AX!+#KAzr+!7K#E|Dt;o!S8Yd#Y3%Yb&l#>
zdfeGRv4o$^