windtear 追求完美

http://windtear.net/archives/2005/03/17/000603.html

下午了解了Raritan关于KVM串口部分的信息

模拟数字两个系列中 SX 属于数字系列
Paragon + IP-Reach
KX SX KSX (S 比 K 就好在没用用户数限制)

CommanderCenter 的全局管理 单点登录 票据漫游
我也问了几个问题

晚上随便跑了两个 mod_proxy 数据看了看
apache_1.3.33/htdocs/manual/mod/mod_proxy.html

Basic Examples

The examples below are only a very basic idea to help you get started. Please read the documentation on the individual directives.

Forward Proxy

ProxyRequests On
ProxyVia On

<Directory proxy:*>
Order deny,allow
Deny from all
Allow from internal.example.com
</Directory>

CacheRoot "/usr/local/apache/proxy"
CacheSize 5
CacheGcInterval 4
CacheMaxExpire 24
CacheLastModifiedFactor 0.1
CacheDefaultExpire 1
NoCache a-domain.com another-domain.edu joes.garage-sale.com

Reverse Proxy

ProxyRequests Off

ProxyPass /foo http://foo.example.com/bar
ProxyPassReverse /foo http://foo.example.com/bar

Controlling access to your proxy

You can control who can access your proxy via the normal <Directory> control block using the following example:

<Directory proxy:*>
Order Deny,Allow
Deny from all
Allow from yournetwork.example.com
</Directory>

A <Files> block will also work, and is the only method known to work for all possible URLs in Apache versions earlier than 1.2b10.

For more information, see mod_access.

Strictly limiting access is essential if you are using a forward proxy (using the ProxyRequests directive). Otherwise, your server can be used by any client to access arbitrary hosts while hiding his or her true identity. This is dangerous both for your network and for the Internet at large. When using a reverse proxy (using the ProxyPass directive with ProxyRequests Off), access control is less critical because clients can only contact the hosts that you have specifically configured.