i r e m e n t c h e c k e r s c r i p t at t h e f ol l ow i n g UR L i n a W e b b r ow s e r : http://hostname/path/to/yii/requirements/index.php T h e m i n i m u m r e q u i r e m e n t b y Yi i Yi i ap p l i c at i on b y ac c e s s i n g t h e f ol l ow i n g UR L i n a W e b b r ow s e r : http://hostname/testdrive/index.php As w e c an s e e , t h e ap p l i c at i on h as t h r e e p age generate admin.php generate _form.php Crud ’user’ has been successfully created. You may access it via: http://hostname/path/to/index.php?r=user I n t h e ab ov e , w e u s e t h e yiic shell c om m an d t

06.HTTP & AJAX 19 décembre 2023 Développement web il3 HTTP & AJAX HE-Arc (DGR) 2022 HyperText Transfer Protocol • Protocole application : invention www en 1990 (v0.9) – Connexion, GET, réponse, fermeture • HTTP 1.0 (1996) – Entêtes de requête (Host, Referer, User-Agent, …) et réponse (Content-Type, Set- Cookie, Location, …) • HTTP 1.1 (1997) – Nouveaux entêtes (Keep-alive, pipelining, cache Host obligatoire • HTTP 2.01 (2015) – Binaire, multiplexage connexions, compression entêtes, push, … – Supporté par presque tous2 les navigateurs, une majorité de serveurs • HTTP 3.03 (2019) – UDP,

Cookie, Session 与HTTP请求 杨亮 Web基本流程 PC Mobile 服务器 （Apache） (IIS) 后端脚本 （PHP） （JSP） （ASP） 数据库 （MySQL） （Oracle） （Access） HTTP 请求 对应⽂文件 获取数据 返回数据 返回⻚页⾯面 返回⻚页⾯面 请求⻚页⾯面 服务器端 客户端 html css 如果⼀一家咖啡店，买五杯送⼀一杯 信息存在哪⾥里？ 超⽂文本传输协议 HTTP HyperText Transfer Protocol ⽆无状态 Cookie Session 头部 内容 （html） Cookie 保存在浏览器端的⽤用户数据，⽤用以进⾏行会话控制 浏览器端脚本(JavaScript)设定Cookie 服务器端程序(PHP)通过HTTP请求命令浏览器设定Cookie 浏览器向服务器发送请求时会附加上相应的Cookie value1 name2 value2 name3 value3 name4 value4 五⼤大要素：名字、值、域、路径、过期时间 $_COOKIE[name] 所有Cookie都是放到http头信息中 服务器 PHP 浏览器 Cookie Set-Cookie:user=stefyang Cookie:user=stefyang time() 当前时间 time()+60*60

tiny server of mine and was ~40% faster with only 20 minutes of work.” “I feel like I’m just talking HTTP at last, with nothing in the middle. Falcon seems like the requests of backend.” “The source code objects DRY request processing via middleware components and hooks Strict adherence to RFCs Idiomatic HTTP error responses Straightforward exception handling Snappy testing with WSGI/ASGI helpers and mocks Utilities Custom HTTP Methods Inspect Module Using Inspect Functions Inspect Functions Reference Router Inspection Information Classes Visitor Classes Utilities URI Date and Time HTTP Status Async Other

tiny server of mine and was ~40% faster with only 20 minutes of work.” “I feel like I’m just talking HTTP at last, with nothing in the middle. Falcon seems like the requests of backend.” “The source code DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses • Straightforward exception handling • Snappy testing with WSGI/ASGI helpers and DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses • Straightforward exception handling • Snappy testing with WSGI/ASGI helpers and

tiny server of mine and was ~40% faster with only 20 minutes of work.” “I feel like I’m just talking HTTP at last, with nothing in the middle. Falcon seems like the requests of backend.” “The source code objects DRY request processing via middleware components and hooks Strict adherence to RFCs Idiomatic HTTP error responses Straightforward exception handling Snappy testing with WSGI/ASGI helpers and mocks Utilities Custom HTTP Methods Inspect Module Using Inspect Functions Inspect Functions Reference Router Inspection Information Classes Visitor Classes Utilities URI Date and Time HTTP Status Async Other

tiny server of mine and was ~40% faster with only 20 minutes of work.” “I feel like I’m just talking HTTP at last, with nothing in the middle. Falcon seems like the requests of backend.” “The source code DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses • Straightforward exception handling • Snappy testing with WSGI/ASGI helpers and DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses • Straightforward exception handling • Snappy testing with WSGI/ASGI helpers and

tiny server of mine and was ~40% faster with only 20 minutes of work.” “I feel like I’m just talking HTTP at last, with nothing in the middle. Falcon seems like the requests of backend.” “The source code objects DRY request processing via middleware components and hooks Strict adherence to RFCs Idiomatic HTTP error responses Straightforward exception handling Snappy testing with WSGI/ASGI helpers and mocks Utilities Custom HTTP Methods Inspect Module Using Inspect Functions Inspect Functions Reference Router Inspection Information Classes Visitor Classes Utilities URI Date and Time HTTP Status Async Other

tiny server of mine and was ~40% faster with only 20 minutes of work.” “I feel like I’m just talking HTTP at last, with nothing in the middle. Falcon seems like the requests of backend.” “The source code DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses • Straightforward exception handling • Snappy testing with WSGI/ASGI helpers and DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses • Straightforward exception handling • Snappy testing with WSGI/ASGI helpers and

tiny server of mine and was ~40% faster with only 20 minutes of work.” “I feel like I’m just talking HTTP at last, with nothing in the middle. Falcon seems like the requests of backend.” “The source code DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses • Straightforward exception handling • Snappy testing with WSGI/ASGI helpers and DRY request processing via middleware components and hooks • Strict adherence to RFCs • Idiomatic HTTP error responses • Straightforward exception handling • Snappy testing with WSGI/ASGI helpers and