Couche application HTTP. Computer Networks. Tanenbaum Computer Networking. Kurose&Ross. Carole Delporte M2-Protocoles Internet 2-1

Transcription

1 Couche application HTTP Computer Networks. Tanenbaum Computer Networking. Kurose&Ross M2-Protocoles Internet 2-1

2 Http: Principes M2-Protocoles Internet 2-2

3 Web et HTTP v Une page web page contient des objets v Objet : fichier HTML, images JPEG, applet, fichiers audio, v Une page web page consiste en un fichier de base HTML contenant des objets référencés v Chaque objet est adressable par une URL (Uniform Resource Locator) host name path name M2-Protocoles Internet 2-3

4 URL: Example: Protocol Server Page on server Our focus Common URL protocols M2-Protocoles Internet 2-4

5 HTTP overview HTTP: hypertext transfer protocol v Web s application layer protocol v client/server model client: browser that requests, receives, (using HTTP protocol) and displays Web objects server: Web server sends (using HTTP protocol) objects in response to requests PC running Firefox browser iphone running Safari browser server running Apache Web server M2-Protocoles Internet 2-5

6 Content type Content type is identified by MIME types Browser takes the appropriate action to display Plug-ins / helper apps extend browser for new types M2-Protocoles Internet

7 HTTP overview uses TCP: v client initiates TCP connection (creates socket) to server, port 80 v server accepts TCP connection from client v HTTP messages (application-layer protocol messages) exchanged between browser (HTTP client) and Web server (HTTP server) v TCP connection closed HTTP is stateless v server maintains no information about past client requests protocols that maintain state are complex! v v past history (state) must be maintained if server/client crashes, their views of state may be inconsistent, must be reconciled M2-Protocoles Internet 2-7

8 Overview Steps a client (browser) takes to follow a hyperlink: Determine the protocol (HTTP) Ask DNS for the IP address of server Make a TCP connection to server Send request for the page; server sends it back Fetch other URLs as needed to display the page Close idle TCP connections Steps a server takes to serve pages: Accept a TCP connection from client Get page request and map it to a resource (e.g., file name) Get the resource (e.g., file from disk) Send contents of the resource to the client. Release idle TCP connections M2-Protocoles Internet

9 HTTP connections non-persistent HTTP v at most one object sent over TCP connection connection then closed v downloading multiple objects required multiple connections persistent HTTP v multiple objects can be sent over single TCP connection between client, server M2-Protocoles Internet 2-9

10 Non-persistent HTTP suppose user enters URL: time 1a. HTTP client initiates TCP connection to HTTP server (process) at on port HTTP client sends HTTP request message (containing URL) into TCP connection socket. Message indicates that client wants object somedepartment/ home.index (contains text, references to 10 jpeg images) 1b. HTTP server at host waiting for TCP connection at port 80. accepts connection, notifying client 3. HTTP server receives request message, forms response message containing requested object, and sends message into its socket M2-Protocoles Internet 2-10

11 Non-persistent HTTP (cont.) 5. HTTP client receives response message containing html file, displays html. Parsing html file, finds 10 referenced jpeg objects 4. HTTP server closes TCP connection. time 6. Steps 1-5 repeated for each of 10 jpeg objects M2-Protocoles Internet 2-11

12 Non-persistent HTTP: response time RTT (definition): time for a small packet to travel from client to server and back HTTP response time: v one RTT to initiate TCP connection v one RTT for HTTP request and first few bytes of HTTP response to return v file transmission time v non-persistent HTTP response time = 2RTT+ file transmission time initiate TCP connection RTT request file RTT file received time time time to transmit file M2-Protocoles Internet 2-12

13 Persistent HTTP non-persistent HTTP issues: v requires 2 RTTs per object v OS overhead for each TCP connection v browsers often open parallel TCP connections to fetch referenced objects persistent HTTP: v server leaves connection open after sending response v subsequent HTTP messages between same client/server sent over open connection v client sends requests as soon as it encounters a referenced object v as little as one RTT for all the referenced objects M2-Protocoles Internet 2-13

14 HTTP request message v two types of HTTP messages: request, response v HTTP request message: ASCII (human-readable format) request line (GET, POST, HEAD commands) header lines carriage return, line feed at start of line indicates end of header lines carriage return character line-feed character GET /index.html HTTP/1.1\r\n Host: www-net.cs.umass.edu\r\n User-Agent: Firefox/3.6.10\r\n Accept: text/html,application/xhtml+xml\r\n Accept-Language: en-us,en;q=0.5\r\n Accept-Encoding: gzip,deflate\r\n Accept-Charset: ISO ,utf-8;q=0.7\r\n Keep-Alive: 115\r\n Connection: keep-alive\r\n \r\n M2-Protocoles Internet 2-14

15 HTTP request message: general format method sp URL sp version cr lf header field name value cr lf ~ ~ request line header lines header field name cr lf value cr lf entity body ~ ~ body M2-Protocoles Internet 2-15

16 HTTP Headers: Function Browser capabilities (client à server) Caching related (mixed directions) Browser context (client à server) Content delivery (server à client) Example Headers User-Agent, Accept, Accept-Charset, Accept- Encoding, Accept-Language If-Modified-Since, If-None-Match, Date, Last- Modified, Expires, Cache-Control, ETag Cookie, Referer, Authorization, Host Content-Encoding, Content-Length, Content-Type, Content-Language, Content-Range, Set-Cookie M2-Protocoles Internet

17 Uploading form input POST method: v web page often includes form input v input is uploaded to server in entity body URL method: v uses GET method v input is uploaded in URL field of request line: M2-Protocoles Internet 2-17

18 Method types HTTP/1.0: v GET v POST v HEAD asks server to leave requested object out of response HTTP/1.1: v GET, POST, HEAD v PUT uploads file in entity body to path specified in URL field v DELETE deletes file specified in the URL field M2-Protocoles Internet 2-18

19 HTTP Request methods. Fetch a page Used to send input data to a server program M2-Protocoles Internet

20 HTTP response message status line (protocol status code status phrase) header lines data, e.g., requested HTML file HTTP/ OK\r\n Date: Sun, 26 Sep :09:20 GMT\r\n Server: Apache/ (CentOS)\r\n Last-Modified: Tue, 30 Oct :00:02 GMT \r\n ETag: "17dc6-a5c-bf716880"\r\n Accept-Ranges: bytes\r\n Content-Length: 2652\r\n Keep-Alive: timeout=10, max=100\r\n Connection: Keep-Alive\r\n Content-Type: text/html; charset=iso \r\n \r\n data data data data data... M2-Protocoles Internet 2-20

21 HTTP response status codes v status code appears in 1st line in server-toclient response message. v some sample codes: 200 OK request succeeded, requested object later in this msg 301 Moved Permanently requested object moved, new location specified later in this msg (Location:) 400 Bad Request request msg not understood by server 404 Not Found requested document not found on this server 505 HTTP Version Not Supported M2-Protocoles Internet 2-21

22 HTTP Response codes tell the client how the request fared: M2-Protocoles Internet

23 Trying out HTTP (client side) for yourself 1. Telnet to your favorite Web server: telnet 80 opens TCP connection to port 80 (default HTTP server port) at cis.poly.edu. anything typed in sent to port 80 at cis.poly.edu 2. type in a GET HTTP request: GET /~cd/ HTTP/1.1 Host: by typing this in (hit carriage return twice), you send this minimal (but complete) GET request to HTTP server 3. look at response message sent by HTTP server! M2-Protocoles Internet 2-23

24 $ telnet 80 Trying Connected to Escape character is '^]'. GET /~cd/ HTTP/1.1 Host: HTTP/ OK Date: Fri, 17 Oct :32:29 GMT Server: Apache Last-Modified: Tue, 30 Sep :23:33 GMT ETag: "23f ace01900c" Accept-Ranges: bytes Content-Length: Content-Type: text/html <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional// EN"> <html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com... M2-Protocoles Internet 2-24

25 M2-Protocoles Internet 2-25

26 User-server state: cookies many Web sites use cookies four components: 1) cookie header line of HTTP response message 2) cookie header line in next HTTP request message 3) cookie file kept on user s host, managed by user s browser 4) back-end database at Web site example: v Susan always access Internet from PC v visits specific e-commerce site for first time v when initial HTTP requests arrives at site, site creates: unique ID entry in backend database for ID M2-Protocoles Internet 2-26

27 Cookies: keeping state (cont.) client server ebay 8734 cookie file ebay 8734 amazon 1678 usual http request msg usual http response set-cookie: 1678 Amazon server creates ID 1678 for user create entry backend database usual http request msg cookie: 1678 usual http response msg cookiespecific action access one week later: ebay 8734 amazon 1678 usual http request msg cookie: 1678 usual http response msg cookiespecific action access M2-Protocoles Internet 2-27

28 Cookies (continued) what cookies can be used for: v authorization v shopping carts v recommendations v user session state (Web ) aside cookies and privacy: v cookies permit sites to learn a lot about you v you may supply name and to sites how to keep state : v protocol endpoints: maintain state at sender/receiver over multiple transactions v cookies: http messages carry state M2-Protocoles Internet 2-28

29 Caching To scale performance, Web servers can use: Caching, multiple threads, and a front end M2-Protocoles Internet

30 Caching Server steps, revisited: Resolve name of Web page requested Perform access control on the Web page Check the cache Fetch requested page from disk or run program Determine the rest of the response Return the response to the client Make an entry in the server log M2-Protocoles Internet

31 Web caches (proxy server) goal: satisfy client request without involving origin server v user sets browser: Web accesses via cache v browser sends all HTTP requests to cache object in cache: cache returns object else cache requests object from origin server, then returns object to client client client proxy server origin server origin server M2-Protocoles Internet 2-31

32 More about Web caching v cache acts as both client and server server for original requesting client client to origin server v typically cache is installed by ISP (university, company, residential ISP) why Web caching? v reduce response time for client request v reduce traffic on an institution s access link v Internet dense with caches: enables poor content providers to effectively deliver content (so too does P2P file sharing) M2-Protocoles Internet 2-32

33 Caching example: assumptions: v v v v avg object size: 1Mbits avg request rate from browsers to origin servers:15request/sec avg RTT from institutional router to any origin server: 2 sec access link rate: 15 Mbps consequences: v Traffic intensity on the LAN : 15% problem! v access link utilization = 100% v total delay = Internet delay + access delay + LAN delay = 2 sec + minutes + millisecs institutional network public Internet 15 Mbps access link origin servers 100 Mbps LAN M2-Protocoles Internet 2-33

34 Caching example: fatter access link assumptions: v v v v avg object size: 1Mbits avg request rate from browsers to origin servers:15/sec RTT from institutional router to any origin server: 2 sec access link rate: 15 Mbps consequences: v LAN utilization: 15% v access link utilization = 100% 10% v total delay = Internet delay + access delay + LAN delay = 2 sec + minutes + msecs msecs origin servers 150 Mbps 15 Mbps 150 Mbps access link Cost: increased access link speed (not cheap!) institutional network public Internet 100Mbps LAN M2-Protocoles Internet 2-34

35 Caching example: install local cache assumptions: v v v v avg object size: 1Mbits avg request rate from browsers to origin servers:15/sec RTT from institutional router to any origin server: 2 sec access link rate: 15 Mbps consequences: v LAN utilization: 15% v access link utilization = 100%? v total delay = Internet? delay + access delay + LAN delay How to compute link = 2 sec + minutes + usecs utilization, delay? Cost: web cache (cheap!) institutional network public Internet 15 Mbps access link origin servers 100 Mbps LAN local web cache M2-Protocoles Internet 2-35

36 Caching example: install local cache Calculating access link utilization, delay with cache: v suppose cache hit rate is % requests satisfied at cache, 60% requests satisfied at origin v access link utilization: 60% of requests use access link access link utilization =60% v total delay = 0.6 * (delay from origin servers) +0.4 * (delay when satisfied at cache) = 0.6 (2.01) (~msecs) = ~ 1.2 secs less than with 150 Mbps link (and cheaper too!) institutional network public Internet 15 Mbps access link origin servers 100 Mbps LAN local web cache M2-Protocoles Internet 2-36

37 Conditional GET v Goal: don t send object if cache has up-to-date cached version no object transmission delay lower link utilization v cache: specify date of cached copy in HTTP request If-modified-since: <date> v server: response contains no object if cached copy is up-to-date: HTTP/ Not Modified client HTTP request msg If-modified-since: <date> HTTP response HTTP/ Not Modified HTTP request msg If-modified-since: <date> HTTP response HTTP/ OK <data> server object not modified before <date> object modified after <date> M2-Protocoles Internet 2-37

38 Content distribution networks (CDNs) Content replication v v Challenging to stream large files (e.g., video) from single origin server in real time Solution: replicate content at hundreds of servers throughout Internet content downloaded to CDN servers ahead of time placing content close to user avoids impairments (loss, delay) of sending content over long paths CDN server typically in edge/ access network CDN server in S. America origin server in North America CDN distribution node CDN server in Europe CDN server in Asia M2-Protocoles Internet-38 M2-Protocoles Internet

39 Content distribution networks (CDNs) Content replication v v CDN (e.g., Akamai) customer is the content provider (e.g., CNN) CDN replicates customers content in CDN servers. When provider updates content, CDN updates servers origin server in North America CDN distribution node CDN server in S. America CDN server in Europe CDN server in Asia M2-Protocoles Internet -39

40 CDN example HTTP request for Origin server CDNs authoritative DNS server DNS query for origin server ( v distributes HTML v replaces: with sports/ruth.gif Nearby CDN server HTTP request for CDN company (cdn.com) distributes gif files uses its authoritative DNS server to route redirect requests M2 M2-Protocoles Internet Internet -40

41 More about CDNs routing requests v CDN creates a map, indicating distances from leaf ISPs and CDN nodes v when query arrives at authoritative DNS server: server determines ISP from which query originates uses map to determine best CDN server v CDN nodes create application-layer overlay network M2-Protocoles Internet -41

42 Static Web Pages Static Web pages are simply files Have the same contents for each viewing Can be visually rich and interactive nonetheless: HTML that mixes text and images Forms that gather user input Style sheets that tailor presentation Vector graphics, videos, and more (over)... M2-Protocoles Internet

43 Static Web Pages Progression of features through HTML 5.0 M2-Protocoles Internet

44 Dynamic Pages & Web Applications Dynamic pages are generated by programs running at the server (with a database) and the client E.g., PHP at server, JavaScript at client Pages vary each time like using an application M2-Protocoles Internet

45 Dynamic Pages & Web Applications Web page that gets form input and calls a server program PHP server program that creates a custom Web page PHP calls Resulting Web page (for inputs Barbara and 32 ) M2-Protocoles Internet

46 Dynamic Pages JavaScript program produces result page in the browser First page with form, gets input and calls program above M2-Protocoles Internet 2-46

47 Dynamic Pages & Web Applications The difference between server and client programs Server-side scripting with PHP Client-side scripting with JavaScript M2-Protocoles Internet

48 Dynamic Pages & Web Applications Web applications use a set of technologies that work together, e.g. AJAX: HTML: present information as pages. DOM: change parts of pages while they are viewed. XML: let programs exchange data with the server. Asynchronous way to send and retrieve XML data. JavaScript as a language to bind all this together. M2-Protocoles Internet

49 Dynamic Pages & Web Applications The DOM (Document Object Model) tree represents Web pages as a structure that programs can alter M2-Protocoles Internet

50 Dynamic Pages & Web Applications XML captures document structure, not presentation like HTML. Ex: M2-Protocoles Internet

51 Dynamic Pages & Web Applications Web applications use a set of technologies, revisited: M2-Protocoles Internet

52 The Mobile Web Mobiles (phones, tablets) are challenging as clients: Relatively small screens Limited input capabilities, lengthy input. Network bandwidth is limited Connectivity may be intermittent. Computing power is limited Strategies to handle them: Contents: servers provide mobile-friendly versions; transcoding can also be used Protocols: no real need for specialized protocols; HTTP with header compression sufficient M2-Protocoles Internet

53 apache v Pour pouvoir tester les exemples on utilisera apache logiciel libre disponible sur la plupart des plateformes Le serveur le plus fréquent Prise en charge de nombreux modules, (perl php, python, ruby ) cgi Serveurs virtuels M2-Protocoles Internet 1-53

54 Principes v Le serveur reçoit des requêtes http et renvoie des pages html dans des réponses http Interpréter les requêtes Lancer sur le côté serveur les applications concernées Récupérer les résultats et les transmettre au client v Configuration: httpd.conf (en général dans /etc/apache2 (et par catalogue.htaccess et htpasswd ) par users /etc/apache2/users/nomuser.conf M2-Protocoles Internet 1-54

55 /etc/apache2/httpd.conf # # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept. # # Do not add a slash at the end of the directory path. If you point # ServerRoot at a non-local disk, be sure to specify a local disk on the # Mutex directive, if file-based mutexes are used. If you wish to share the # same ServerRoot for multiple httpd daemons, you will need to change at # least PidFile. # ServerRoot "/usr" M2-Protocoles Internet 2-55

56 # # Listen: Allows you to bind Apache to specific IP addresses and/or # ports, instead of the default. See also the <VirtualHost> # directive. # # Change this to Listen on specific IP addresses as shown below to # prevent Apache from glomming onto all bound IP addresses. # #Listen :80 Listen 80. M2-Protocoles Internet 2-56

57 /etc/apache2/users/remi.conf $ more remi.conf <Directory "/Users/remi/Sites/"> Options Indexes MultiViews AllowOverride None Order allow,deny Allow from all </Directory> M2-Protocoles Internet 2-57

58 Principes v Correspondance entre url et fichiers locaux DocumentRoot: Si DocumentRoot = /Library/WebServer/Documents sera converti en /Library/WebServer/Documents/un/deux.html Pages des utilisateurs UserDir: ~/Sites sera /Users/user/Sites/file.html En plus des alias et des redirections M2-Protocoles Internet 1-58

59 Pour voir v Sur cette machine: /etc/apache2/httpd.conf ServerRoot: /usr DocumentRoot: /Library/WebServer/Documents + fichier de configurations dans «extra» UserDir: Sites M2-Protocoles Internet 1-59

60 CGI v Common Gateway Interface v exécuter du code du côté serveur v Passage de paramètre par la méthode POST ou la méthode GET v Variables d'environnement M2-Protocoles Internet 60

61 Pour Apache v Les executables cgi (dépendant) ScriptAlias /cgi-bin /Library/WebServer/CGI-Executables/ Pour /Library/WebServer/CGI-Executables/exemples/ treat.pl sera exécuté v "Paramètres" POST: transmis sur l'entrée standard (STDIN) GET: variable de l'environnement QUERY_STRING v STDOUT pour la réponse (au moins un MIME type header Content-type: text/html et deux newline) M2-Protocoles Internet 61

62 Exemple v en shell: /Library/WebServer/CGI-Executables/exemples/ exemples/date.cgi #!/bin/sh tmp=`/bin/date` echo "Content-type: text/html\n <HTML><HEAD><TITLE>Script Cgi</TITLE></ HEAD><BODY> <CENTER> <H1>La date courante sur le serveur est</h1> $tmp </CENTER> </BODY> </HTML>" l'url affichera la date M2-Protocoles Internet 62

63 Avec un formulaire: <HTML><HEAD><TITLE>Formulaire simple</title></head> <BODY> <H2>Répondez aux questions suivantes</h2> <FORM ACTION=" METHOD=GET> Prénom : <INPUT TYPE="text" NAME=prenom SIZE=20><BR> Nom : <INPUT TYPE="text" NAME=nom SIZE=20><BR> Age : <SELECT NAME=age> <OPTION>- de 18 ans <OPTION>19 à 40 ans <OPTION>41 à 60 ans <OPTION>+ de 60 ans </SELECT><BR> <INPUT TYPE=submit VALUE="Envoyer"> <INPUT TYPE=reset VALUE="Remettre à zéro"> </FORM> </BODY> M2-Protocoles Internet 63

64 Résultat v par la méthode get codage des paramètres: v prenom=carole&nom=delporte&age=41 +%C3%A0+60+ans v le navigateur génère l'url: prenom=carole&nom=delporte&age=41+%c3%a0+60+ans %C3%A0+60+ans Avec la méthode POST Prenom=Carole&nom=Delporte&age=41+%C3%A0+60+ans M2-Protocoles Internet 64

65 Traitement en perl v /Library/WebServer/CGI-Executables/exemples/ treat.pl v prenom=carole&nom=delporte&age=41+%c3%a0+60+ans %C3%A0+60+ans M2-Protocoles Internet 65

66 Paramètres v Les paramètres sont accessibles par l'intermédiaire de la variable d'environnement QUERY_STRING M2-Protocoles Internet 66

67 #!/usr/bin/perl # les donnees sont envoyees par methode GET # donc on recupere les donnees dans la variable # d'environnement QUERY_STRING $buffer=$env{"query_string"}; # Si POST: $buffer= <STDIN>; # on split la chaine de donnees en des paires name=value local(@champs) = split(/&/, $buffer); local($donnees) = "»; # affichage du debut du code HTML printf STDOUT "Content-type: text/html\n\n"; printf STDOUT "<HTML><HEAD>"; printf STDOUT "<TITLE>Reponse au questionnaire</title>"; printf STDOUT "</HEAD>"; printf STDOUT "<BODY BGCOLOR=\"#ffffff\">»; M2-Protocoles Internet 2-67

68 printf STDOUT "<H1>R<E9>sultat du traitement de votre questionnaire</ H1>"; printf STDOUT "<H2>Chaine de donn<e9>es re<e7>ue par le programme</h2>"; printf STDOUT "QUERY_STRING <STRONG>%s</STRONG>",$buffer; printf STDOUT "<H2>Liste des informations d<e9>cod<e9>es</h2>"; printf STDOUT "<UL>"; printf STDOUT "<BL>"; # recuperation et mise en forme des donnees # on parcourt la liste des paires name=value foreach $i (0.. $#champs) { # On convertit les plus en espaces $champs[$i] =~ s/\+/ /g; M2-Protocoles Internet 2-68

69 # On separe chaque champ en une cle et sa valeur ($key, $val) = split(/=/,$champs[$i],2); # On convertit les %XX de leur valeur hexadecimale en alphanumerique $key =~ s/%(..)/pack("c",hex($1))/ge; $val =~ s/%(..)/pack("c",hex($1))/ge; } # on affiche le resultat printf STDOUT "<LI><STRONG>%s:</STRONG>%s\n",$key,$val; printf STDOUT "</BL>"; printf STDOUT "</UL>"; printf STDOUT "</BODY>"; printf STDOUT "</HTML>"; M2-Protocoles Internet 2-69

70 Variables d'environnement v SERVER_SOFTWARE Le nom et la version du serveur HTTP répondant à la requête. (Format : nom/version) v SERVER_NAME Le nom d'hôte, alias DNS ou adresse IP du serveur. v GATEWAY_INTERFACE La révision de la spécification CGI que le serveur utilise. (Format : CGI/révision) M2-Protocoles Internet 70

71 Variables v v v v v SERVER_PROTOCOL Le nom et la révision du protocole dans lequel la requête a été faite (Format : protocole/révision) SERVER_PORT Le numéro de port sur lequel la requête a été envoyée. REQUEST_METHOD La méthode utilisée pour faire la requête. Pour HTTP, elle contient généralement «GET» ou «POST». PATH_INFO Le chemin supplémentaire du script tel que donné par le client. Par exemple, si le serveur héberge le script «/cgi-bin/ monscript.cgi» et que le client demande l'url « serveur.org/cgi-bin/monscript.cgi/marecherche», alors PATH_INFO contiendra «marecherche». PATH_TRANSLATED Contient le chemin demandé par le client après que les conversions virtuel physique aient été faites par le serveur. M2-Protocoles Internet 71

72 Variables v v v v v SCRIPT_NAME Le chemin virtuel vers le script étant exécuté. Exemple : «/cgibin/script.cgi» QUERY_STRING Contient tout ce qui suit le «?» dans l'url envoyée par le client. Toutes les variables provenant d'un formulaire envoyé avec la méthode «GET» sera contenue dans le QUERY_STRING sous la forme «var1=val1&var2=val2&...». REMOTE_HOST Le nom d'hôte du client. Si le serveur ne possède pas cette information (par exemple, lorsque la résolution DNS inverse est désactivée), REMOTE_HOST sera vide. REMOTE_ADDR L'adresse IP du client. AUTH_TYPE Le type d'identification utilisé pour protéger le script (s il est protégé et si le serveur supporte l'identification). M2-Protocoles Internet 72

73 Variables v v v v REMOTE_USER Le nom d'utilisateur du client, si le script est protégé et si le serveur supporte l'identification. REMOTE_IDENT Nom d'utilisateur (distant) du client faisant la requête. Le serveur doit supporter l'identification RFC 931. Cette variable devraient être utilisée à des fins de journaux seulement. CONTENT_TYPE Le type de contenu attaché à la requête, si des données sont attachées (comme lorsqu'un formulaire est envoyé avec la méthode «POST»). CONTENT_LENGTH La longueur du contenu envoyé par le client. M2-Protocoles Internet 73

74 Variables v HTTP_ACCEPT Les types de données MIME que le client accepte de recevoir. Exemple : text/*, image/jpeg, image/png, image/*, */* v HTTP_ACCEPT_LANGUAGE Les langages dans lequel le client accepte de recevoir la réponse. Exemple : fr_ca, fr v HTTP_USER_AGENT Le navigateur utilisé par le client. Exemple : Mozilla/5.0 (compatible; Konqueror/3; Linux) M2-Protocoles Internet 74

75 <HTML><HEAD><TITLE>Formulaire simple</title></head> <BODY> <H2>Repondez aux questions suivantes</h2> <FORM ACTION=" METHOD=POST> Prenom : <INPUT TYPE="text" NAME=prenom SIZE=20><BR> Nom : <INPUT TYPE="text" NAME=nom SIZE=20><BR> Age : <SELECT NAME=age> <OPTION>- de 18 ans <OPTION>19 à 40 ans <OPTION>41 à 60 ans <OPTION>+ de 60 ans </SELECT><BR> M2-Protocoles Internet 2-75

76 <INPUT TYPE=submit VALUE="Envoyer"> <INPUT TYPE=reset VALUE="Remettre a zero"> </FORM> </BODY> M2-Protocoles Internet 2-76

77 #!/usr/bin/perl $buffer=$env{"server_software"}; $buffer1=$env{"server_name"}; $buffer2=$env{"gateway_interface"}; $buffer3=$env{"server_protocol"}; $buffer4=$env{"server_port"}; $buffer5=$env{"request_method"}; $buffer6=$env{"path_info"}; $buffer7=$env{"path_translated"}; $buffer8=$env{"script_name"}; $buffer9=$env{"query_string"}; $buffer10=$env{"remote_host"}; M2-Protocoles Internet 2-77

78 $buffer11=$env{"remote_addr"}; $buffer12=$env{"auth_type"}; $buffer13=$env{"remote_user"}; $buffer14=$env{"remote_ident"}; $buffer15=$env{"content_type"}; $buffer16=$env{"content_length"}; $buffer17=$env{"http_accept"}; $buffer18=$env{"http_accept_language"}; $buffer19=$env{"http_user_agent"}; M2-Protocoles Internet 2-78

79 # affichage du debut du code HTML printf STDOUT "Content-type: text/html\n\n"; printf STDOUT "<HTML><HEAD>"; printf STDOUT "<TITLE>Reponse au questionnaire</title>"; printf STDOUT "</HEAD>"; printf STDOUT "<BODY BGCOLOR=\"#ffffff\">"; printf STDOUT "<H1>Var de l'environnement</h1>"; printf STDOUT "QUERY_STRING <STRONG>%s</STRONG>",$buffer; printf STDOUT "<BR>"; printf STDOUT "QUERY_NAME <STRONG>%s</STRONG>",$buffer1; printf STDOUT "<BR>"; printf STDOUT "GATEWAY_INTERFACE <STRONG>%s</STRONG>",$buffe M2-Protocoles Internet 2-79

80 printf STDOUT "<BR>"; printf STDOUT "SERVER_PROTOCOL <STRONG>%s</STRONG>",$buffer3 printf STDOUT "<BR>"; printf STDOUT "SERVER_PORT <STRONG>%s</STRONG>",$buffer4; printf STDOUT "<BR>"; printf STDOUT "REQUEST_METHOD <STRONG>%s</STRONG>",$buffer5; printf STDOUT "<BR>"; printf STDOUT "PATH_INFO <STRONG>%s</STRONG>",$buffer6; printf STDOUT "<BR>"; printf STDOUT "PATH_TRANSLATED <STRONG>%s</STRONG>",$buffer7; printf STDOUT "<BR>"; printf STDOUT "SCRIPT_NAME printf STDOUT "<BR>»; <STRONG>%s</STRONG>",$buffer8; M2-Protocoles Internet 2-80

81 printf STDOUT "QUERY_STRING <STRONG>%s</STRONG>",$buffer9; printf STDOUT "<BR>"; printf STDOUT "REMOTE_HOST <STRONG>%s</STRONG>",$buffer10; printf STDOUT "<BR>"; printf STDOUT "REMOTE_ADDR <STRONG>%s</STRONG>",$buffer11; printf STDOUT "<BR>"; printf STDOUT "AUTH_TYPE <STRONG>%s</STRONG>",$buffer13; printf STDOUT "<BR>"; printf STDOUT "REMORE_USER <STRONG>%s</STRONG>",$buffer13; printf STDOUT "<BR>"; printf STDOUT "REMOTE_IDENT <STRONG>%s</STRONG>",$buffer14; printf STDOUT "<BR>»; M2-Protocoles Internet 2-81

82 printf STDOUT "CONTENT_TYPE <STRONG>%s</STRONG>",$buffer15; printf STDOUT "<BR>"; printf STDOUT "CONTENT_LENGTH <STRONG>%s</STRONG>",$buffer16 printf STDOUT "<BR>"; printf STDOUT "HTTP_ACCEPT <STRONG>%s</STRONG>",$buffer17; printf STDOUT "<BR>"; printf STDOUT "HTTP_ACCEPT_LANGUAGE <STRONG>%s</STRONG>", printf STDOUT "<BR>"; printf STDOUT "HTTP_USER_AGENT <STRONG>%s</STRONG>",$buffer1 printf STDOUT "</BODY>"; printf STDOUT "</HTML>"; M2-Protocoles Internet 2-82

83 On obtient Var de l'environnement QUERY_STRING Apache/2.4.9 (Unix) QUERY_NAME localhost GATEWAY_INTERFACE CGI/1.1 SERVER_PROTOCOL HTTP/1.1 SERVER_PORT 80 REQUEST_METHOD POST PATH_INFO PATH_TRANSLATED SCRIPT_NAME /cgi-bin/exemples/affiche.pl QUERY_STRING REMOTE_HOST REMOTE_ADDR ::1 M2-Protocoles Internet 2-83

84 On obtient AUTH_TYPE REMORE_USER REMOTE_IDENT CONTENT_TYPE application/x-www-form-urlencoded CONTENT_LENGTH 42 HTTP_ACCEPT text/html,application/xhtml+xml,application/ xml;q=0.9,image/webp,*/*;q=0.8 HTTP_ACCEPT_LANGUAGE fr-fr,fr;q=0.8,en- US;q=0.6,en;q=0.4 HTTP_USER_AGENT Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_0) AppleWebKit/ (KHTML, like Gecko) Chrome/ Safari/ M2-Protocoles Internet 2-84

85 Compléments Javascript v Code qui s'exécute du côté du client calcul local contrôle d'une zone de saisie affichage d'alerte fenêtres menus etc.. v Balise : <SCRIPT languge="javascript1.2"> le code... </SCRIPT> M2-Protocoles Internet 85

86 Exemple: bonjour <HTML><HEAD> <TITLE>Très facile</title> </HEAD> <SCRIPT language="javascript1.2"> function bonjour() { alert ("Bonjour madame, bonjour monsieur"); } </SCRIPT> <BODY bgcolor="white" onload="bonjour();"> <H1>Bonjour</H1> </BODY></HTML> M2-Protocoles Internet 86

87 Un peu plus: minicalcul <HTML> <HEAD> <TITLE>Petit calcul</title> </HEAD> <BODY bgcolor='white'> <script language='javascript1.2' src='calcul.js'></script> <script language='javascript1.2' src='fenetre.js'></script> <script language='javascript1.2' src='ctrl.js'></script> <CENTER><H1>Calcul</H1></CENTER> Un petit exemple de formulaire. <P> Création d'une <A href='#a' onclick='affichedoc();'>fenêtre avec JavaScript</A> M2-Protocoles Internet 87

88 Suite <FORM ACTION='Simul.html' METHOD='POST' NAME='Simul'> <CENTER> <TABLE BORDER=3> <TR><TD>Argument 1 <TD> <INPUT TYPE='TEXT' SIZE=20 NAME='arg1' onchange='calcul();'></tr> <TR><TD>* Argument 2 <TD> <INPUT TYPE='TEXT' SIZE=20 NAME='arg2' onchange='calcul();'> </TR> <TR><TD>Résultat= <TD> <INPUT TYPE='TEXT' SIZE=20 NAME='res' > </TR> </TABLE> <INPUT TYPE='BUTTON' VALUE='Vérifier' onclick='ctrl();'> <INPUT TYPE='RESET' VALUE='Effacer tout' onclick=' if (!confirm("vraiment vous voulez effacer?")) exit;'> </CENTER> </FORM> </BODY> </HTML> M2-Protocoles Internet 88

89 Fichiers js v v { } v un/ctrl.js function ctrl() if (isnan(window.document.simul.res.value )) { alert ("Valeur incorrecte : " + document.simul.res.value + "?"); document.forms[0].res.focus(); } un/calcul.js function calcul() { v1=document.forms[0].arg1.value; v2=document.forms[0].arg2.value; document.forms[0].res.value = v2*v1 ; } M2-Protocoles Internet 89

90 suite et fin v un/fenetre.js function affichedoc() { options = "width=300,height=200"; fenetre = window.open('','mu',options); } fenetre.document.open(); manuel = "<HTML><HEAD><TITLE>Documentation</TITLE></ HEAD>" + "<BODY bgcolor='white'>" + "Il n'y a pas besoin d'aide " + " c'est facile." + " Bonne chance!</body></html>"; fenetre.document.write(manuel); fenetre.document.close(); M2-Protocoles Internet 90

91 Compléments: php v php est un langage de script pour les serveurs webs v de nombreuses fonctions permettent de traiter les requêtes http (en particulier des requêtes concernant des bases de données) v ici on est du côté du serveur M2-Protocoles Internet 91

92 Exemple simple <HTML> <HEAD> <TITLE>Exemple très simple</title> </HEAD> <BODY> <H1>Exemple</H1> le <?php date_default_timezone_set('europe/paris'); echo Date ("j/m/y à H:i:s");?> <P> <?php echo "Client :". $_SERVER['HTTP_USER_AGENT']. "<BR>"; echo "Adresse IP client:".$_server['remote_addr']."<br>"; echo "Server: ". $_SERVER['SERVER_NAME'];?> </BODY></HTML> M2-Protocoles Internet 92

93 Résultat Exemple Le 20/10/2014 à 15:47:25 Client :Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:33.0) Gecko/ Firefox/33.0 Adresse IP client:::1 Server: localhost M2-Protocoles Internet 93

94 Reçu par le client <HTML> <HEAD> <TITLE>Exemple très simple</title> </HEAD> <BODY> <H1>Exemple</H1> Le 20/10/2014 à 15:47:25 <P> Client :Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:33.0) Gecko/ Firefox/33.0<BR>Adresse IP client:::1<br>server: localhost </BODY></HTML> M2-Protocoles Internet 94

95 Php v On est ici côté serveur: les balises <?php> <?> sont interprétées par le serveur (apache par exemple) et servent à générer la page html reçue par le client v Mais surtout php permet d'accéder aux variables d'environnement d'utiliser de nombreuses fonctionnalités sessions, paramètres etc. v Php sert souvent d'interface pour MySql serveur simple de bases de données M2-Protocoles Internet 95

96 Php v pas de typage ni de déclaration des variables v $v est remplacé par la valeur de v (et permet aussi l'affectation) v echo "$v"; v constantes define("pi, ); v types des variables numériques $i=1; $v=3.14; chaînes de caractères (expressions régulières) $nom=»diderot"; ',",{} M2-Protocoles Internet 96

97 php v Variables Locales (à une fonction) Globales Super globales (disponibles dans tout contexte) Static (garde sa valeur) Variables dynamiques (le nom de la variable est une variable) $a='bonjour' $$a='monde' echo "$a ${$a}" echo "$a $bonjour" M2-Protocoles Internet 97

98 php v tableaux indicés $tab[0]="un"; $tab=array("un","deux","trois"); associatifs $m=array("un"=>"one", "deux"=>"two"); $m["trois"]="three"; next() prev() key() current do {echo "Clé=key($m).Valeur= current($m)"} while(next($mes)); foreach($m as $cle =>$val) {echo "Clé=$cle.Valeur=$val";} M2-Protocoles Internet 98

99 php v Mais aussi (php4 et php5) Programmation orientée objets Classes et Objets Liaison dynamique Constructeurs Exceptions M2-Protocoles Internet 99

100 Php v structures de contrôles if if else while do while for foreach break, continue M2-Protocoles Internet 100

101 fonctions function Nom([$arg1, $arg2,...]) { corps } passage par valeur (et par référence &) exemples function Add($i,$j){ $somme= $i + $j; return $somme; } function Add($i,$j,&$somme){ $somme= $i + $j; } M2-Protocoles Internet 101

102 Pour le serveur v tableaux associatifs prédéfinis $_SERVER: environnement serveur REQUEST_METHOD QUERY_STRING CONTENT_LENGTH SERVER_NAME PATH_INFO HTTP_USER_AGENT REMOTE_ADDR REMOTE_HOST REMOTE_USER REMOTE_PASSWORD M2-Protocoles Internet 102

103 Suite v Autres tableaux $_ENV : environnement système $_COOKIE $_GET $_POST $_FILES $_REQUEST (variables des 4 précédents) $_SESSION $GLOBALS les variables globales du script M2-Protocoles Internet 103

104 Cookies et php <?php // Est-ce que le Cookie existe? if (isset($_cookie['compteur'])) { $message = "Vous êtes déjà venu {$_COOKIE['compteur']} fois ". "me rendre visite<br>\n"; // On incrémente le compteur $valeur = $_COOKIE['compteur'] + 1; } else { // Il faut créer le cookie avec la valeur 1 $message = "Bonjour, je vous envoie un cookie<br>\n"; $valeur = 1; } // Envoi du cookie SetCookie ("compteur", $valeur);?> M2-Protocoles Internet 104

105 Cookies et php (fin) <HTML><HEAD> <TITLE>Les cookies</title> </HEAD> <BODY> <H1>Un compteur d'accès au site avec cookie</h1> <?php echo $message;?> </BODY></HTML> M2-Protocoles Internet 105

106 En utilisant les sessions <?php // La fonction session_start fait tout le travail session_start();?> <HTML><HEAD> <TITLE>Les cookies</title> </HEAD> <BODY> <H1>Un compteur d'accès au site avec Session</H1> M2-Protocoles Internet 106

107 Fin <?php if (!isset($_session['cp'])) { $_SESSION['cp']=1; echo "C'estlapremière fois,votre id est:". session_id()."<br>"; } else{ $_SESSION['cp']++; echo "C'est votre ".$_SESSION['cp']." n-ième connexion"; if($_session['cp']>10){ echo "on vous a trop vu"."<br>"; session_destroy(); } }?> </BODY></HTML> M2-Protocoles Internet 107

108 session v session_start() v session_destroy() v session_id() on peut associer des variables à la session par le tableau associatif $_SESSION elle sera accessible à chaque session_start() jusqu'au session_destroy() pour toute connexion qui fournit le session_id(). M2-Protocoles Internet 108