sun's longitude:46 07 38 
¡¤ ÀÚÀ¯°Ô½ÃÆÇ ¡¤ ¹¯°í´äÇϱ⠡¤ ¾ËÆĹ®¼­ ¡¤ RPMS list
¡¤ »ç¿ëÀÚ¹®¼­ ¡¤ ÆÁ/FAQ¸ðÀ½ ¡¤ ¸®´ª½ºLinks ¡¤ ÀÚ·á½Ç
¡¤ ¼­¹öÁ¤º¸ ¡¤ ¿î¿µÀÚ ¡¤ Books/FAQ ¡¤ FreeBSD
 
/board/delete.php:¼Ò½ºº¸±â   
 
¾ËÆĹ®¼­
ÀÚÁÖ Àؾî¸Ô°Å³ª, ¸Þ¸ðÇØ µÑ Çʿ伺ÀÌ ÀÖ´Â ÆÁÀ̳ª ¹®¼­, ±âŸ µîµî
[*** ¾²±â ±ÝÁö´Ü¾î ÆÐÅÏ ***]
±Û º»¹® Áß°£¿¡ ¾÷·ÎµåÇÒ À̹ÌÁö¸¦ Ãß°¡ÇÏ´Â ¹æ¹ý : @@À̹ÌÁöÀ̸§@@
ex) @@foo.gif@@
 ¡Ú ±Û Áö¿ì±â Ç׸ñÀÔ´Ï´Ù. Çѹø ´õ »ý°¢ÇÏ½Ã°í °áÁ¤ÇϽʽÿÀ.!!!
Á¦¸ñ 132 : [Cookie] cookie limit
 À̸§  »êÀÌ [Ȩ]http://linuxchannel.net/
http://wp.netscape.com/newsref/std/cookie_spec.html

There are limitations on the number of cookies that a client can store at any one time. This is a specification of the minimum number of cookies that a client should be prepared to receive and store.

1) 300 total cookies

2) 4 kilobytes per cookie, where the name and the OPAQUE_STRING combine to form the 4 kilobyte limit.

3) 20 cookies per server or domain. (note that completely specified hosts and domains are treated as separate entities and have a 20 cookie limitation for each, not combined)

Servers should not expect clients to be able to exceed these limits. When the 300 cookie limit or the 20 cookie per server limit is exceeded, clients should delete the least recently used cookie. When a cookie larger than 4 kilobytes is encountered the cookie should be trimmed to fit, but the name should remain intact as long as it is less than 4 kilobytes.
2005³â 09¿ù 21ÀÏ 10:10:20 ¼ö(¿ÀÀü)  from 222.106.218.166
0
¾ÏÈ£: °ø¿ë º¸¾È SSL ¼­¹ö°¡ ÁغñµÇ±â Àü±îÁö´Â off ÇÕ´Ï´Ù

apache lighttpd linuxchannel.net 
Copyright 1997-2024. linuxchannel.net. All rights reserved.

Page loading: 0.04(server) + (network) + (browser) seconds