Lighttpdã®ã¤ã³ã¹ãã¼ã« apt-cache searchã§lighttpdãè¦ã¤ãããªãã£ãã®ã§ãlighttpdã®ææ°ãã¼ã¸ã§ã³ãã½ã¼ã¹ããã¤ã³ã¹ãã¼ã«ãã¾ãã
ããã§ã¯Apacheã®mod_proxyã使ã£ã¦80çªãã¼ãã¸ã®ç¹å®ã®ã¢ã¯ã»ã¹ã3000çªãã¼ãã®Lighttpdã«æ¸¡ãã¦ããã¾ããï¼ã¡ãªã¿ã«ãµã¼ãã®Apacheã®ãã¼ã¸ã§ã³ã¯1.3.33ã§ãï¼
ãã®URLã®ãã¼ã¸ã¯è¡¨ç¤ºãããã¨ãåºæ¥ã¾ããã§ããã IQãµã¼ãã¼
Seminarã»Event Googleã¢ããªãã£ã¯ã¹Â å¾¹åºè§£èª¬ã»ããã¼ æææ¯æ1åéå¬Googleã¢ããªãã£ã¯ã¹ã»ããã¼Â å ¥éç·¨ æææ¯æ1åéå¬Googleã¢ããªãã£ã¯ã¹ã»ããã¼Â åæææ³ç·¨ æææ¯æ1åéå¬Googleã¢ããªãã£ã¯ã¹ã»ããã¼Â å¾¹åºè¨å®ç·¨ Access Map詳細
While I was throwing away from bogus data-copy operations from the mod-proxy-core code I stumbled over a simple question: Why do we copy the HTTP response data from the backends at all ? We are just forwarding them in most cases without touching them. How about: HTTP/1.1 200 OK Content-Type: text/html X-LIGHTTPD-send-tempfile: /dev/shm/fcgi-output/j37f467d ⦠and lighty removing the file when it ha
ãç¥ãã
ã©ã³ãã³ã°
ã©ã³ãã³ã°
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}