예전에 찾던 것 중에 php를 통해 무언가를 쓰는게 있었는데
얘 명칭이 helper multiplexer인 듯.
근데 어떤 포맷으로 데이터를 넘겨서 실행하게 하는지에 대해서는 안보이네?
2.4 Helper MultiplexerThe helper multiplexer's purpose is to relieve some of the burden Squid has when dealing with slow helpers. It does so by acting as a middleman between squid and the actual helpers, talking to Squid via the multiplexed concurrent variant of the helper protocol and to the helpers via the non-concurrent variant. Helpers are started on demand, and in theory the muxer can handle up to 1k helpers per instance. It's up to squid to decide how many helpers to start. The muxer knows nothing about the actual messages being passed around, and as such can't really (yet?) compensate for broken helpers. It is not yet able to manage dying helpers, but it will. To configure the multiplexer add its binary name (usually /usr/share/libexec/helper-mux.pl) in front of the name of whichever helper is being multiplexed. It takes the helper binary path and parameters as its own command parameters. The concurrency setting already existing in Squid is used to configure how many child helpers it may run. For example, a traditional configuration is url_rewrite_program /your/redirector.sh url_rewrite_children 5the alternative multiplexer configuration is: url_rewrite_program /usr/share/libexec/helper-mux.pl /your/redirector.sh url_rewrite_children 1 concurrency=5 Helpers which are already concurrent protocol enabled gain little benefit from the multiplexer on most systems. However on some systems where Squid spawning helpers causes excess memory usage the reduction in direct helper spawned by Squid can result in a great reduction in resource use. The helper can be controlled using various signals:
|
[링크 : ftp://ftp.arnes.si/packages/squid/squid-3.2.14-RELEASENOTES.html]
# OPTIONS FOR URL REWRITING
|
# TAG: url_rewrite_program # Specify the location of the executable for the URL rewriter. # Since they can perform almost any function there isn't one included. # # For each requested URL rewriter will receive on line with the format # # URL <SP> client_ip "/" fqdn <SP> user <SP> method <SP> urlgroup # [<SP> kvpairs] <NL> # # In the future, the rewriter interface will be extended with # key=value pairs ("kvpairs" shown above). Rewriter programs # should be prepared to receive and possibly ignore additional # whitespace-separated tokens on each input line. # # And the rewriter may return a rewritten URL. The other components of # the request line does not need to be returned (ignored if they are). # # The rewriter can also indicate that a client-side redirect should # be performed to the new URL. This is done by prefixing the returned # URL with "301:" (moved permanently) or 302: (moved temporarily). # # It can also return a "urlgroup" that can subsequently be matched # in cache_peer_access and similar ACL driven rules. An urlgroup is # returned by prefixing the returned URL with "!urlgroup!". # # By default, a URL rewriter is not used. # #Default: # none |
[링크 : http://alter.org.ua/soft/win/squid_url_rewrite/squid.conf]
[링크 : https://wiki.squid-cache.org/Features/HelperMultiplexer]
'프로그램 사용 > squid' 카테고리의 다른 글
url_rewriter squid (0) | 2019.03.15 |
---|---|
squid hierarchy (0) | 2019.03.14 |
squid log code (0) | 2019.03.01 |
squid hier/none direct 관련 설정 (0) | 2019.02.27 |
squid용 인증서 관련 (인증서 변환하기) (0) | 2019.02.25 |