Ç¥ÁØÈ­ Âü¿©¾È³»

TTAÀÇ Ç¥ÁØÇöȲ

Ȩ > Ç¥ÁØÈ­ °³¿ä > TTAÀÇ Ç¥ÁØÇöȲ

Ç¥ÁعøÈ£ TTAE.OT-10.0358 ±¸Ç¥ÁعøÈ£
Á¦°³Á¤ÀÏ 2024-12-06 ÃÑÆäÀÌÁö 28
ÇѱÛÇ¥Áظí À¥ ¼ÒÄÏ API
¿µ¹®Ç¥Áظí Web Socket API
Çѱ۳»¿ë¿ä¾à ÀÌ Ç¥ÁØ¿¡¼­ ´Ù·ç´Â À¥¼ÒÄÏ(WebSocket) ÇÁ·ÎÅäÄÝÀº ¿ø°Ý È£½ºÆ®¿ÍÀÇ ¾ç¹æÇâ Åë½ÅÀ» °¡´ÉÇÏ°Ô ÇÑ´Ù. À̸¦ À§ÇØ »ç¿ëµÇ´Â º¸¾È ¸ðµ¨Àº ÀϹÝÀûÀ¸·Î À¥ ºê¶ó¿ìÀú¿¡¼­ »ç¿ëµÇ´ÂOBS(Origin-Based Security) º¸¾È ¸ðµ¨À» »ç¿ëÇÑ´Ù. ÀÌ ±â¼úÀÇ ¸ñÀûÀº ´Ù¼öÀÇ HTTP ¿¬°áÀ» ÇÏÁö ¾Ê°í ¼­¹ö¿Í ¾ç¹æÇâ Åë½ÅÀ» ÇÊ¿ä·Î ÇÏ´Â ºê¶ó¿ìÀú ±â¹Ý ¾ÖÇø®ÄÉÀ̼ÇÀ» À§ÇÑ ¸ÞÄ¿´ÏÁòÀ» Á¦°øÇÏ´Â °ÍÀÌ´Ù.
¿µ¹®³»¿ë¿ä¾à This section replaces part of the WebSocket protocol opening handshake client requirement to integrate it with algorithms defined in Fetch.
This way CSP, cookies, HSTS, and other Fetch -related protocols are handled in a single location. Ideally the RFC would be updated with this language, but it is never that easy. The WebSocket API, defined below, uses this language. [WSP] [FETCH]
The way this works is by replacing The WebSocket Protocol's "establish a WebSocket connection' algorithm with a new one that integrates with Fetch. "Establish a WebSocket connection" consists of three algor ithms: setting up a connection, creating and transmiting a handshake request, and validating the handshake response. That layering is different from Fetch, which first creates a handshake, then sets up a connection and transmits the handshake and finally validates the response.
±¹Á¦Ç¥ÁØ
°ü·ÃÆÄÀÏ TTAE.OT-10.0358.pdf TTAE.OT-10.0358.pdf            

ÀÌÀü
PON ȯ°æ¿¡¼­ÀÇ 5G ¸ð¹ÙÀÏ ÇÁ·±Æ®È¦ ¿ä±¸»çÇ×
´ÙÀ½
IALA R0145: ÇØ»ó±³Åë°üÁ¦¼­ºñ½º(VTS)°£ Á¤º¸ ±³È¯ Æ÷¸Ë(IVEF) ¼­ºñ½º