Difference between revisions of "Manual:IP/Proxy"

From MikroTik Wiki
Jump to: navigation, search
(update)
Line 119: Line 119:
 
<p><b>Sub-menu:</b> <code>/ip proxy access</code></p>
 
<p><b>Sub-menu:</b> <code>/ip proxy access</code></p>
 
<p>
 
<p>
 +
Access list is configured like a regular firewall rules. Rules are processed from the top to the bottom. First matching rule specifies decision of what to do with this connection. There is a total of 6 classifiers that specify matching constraints. If none of these classifiers is specified, the particular rule will match every connection.
 +
 +
If connection is matched by a rule, action property of this rule specifies whether connection will be allowed or not. If the particular connection does not match any rule, it will be allowed.
 
</p>
 
</p>
 +
<table class="styled_table">
 +
<tr>
 +
  <th width="40%">Property</th>
 +
  <th >Description</th>
 +
</tr>
 +
<tr>
 +
    <td><var><b>a</b></var> (<em></em>; Default: <b></b>)</td>
 +
    <td></td>
 +
</tr>
 +
</table>
 +
 +
  
 
<h2>Direct Access </h2>
 
<h2>Direct Access </h2>
 
<p><b>Sub-menu:</b> <code>/ip proxy direct</code></p>
 
<p><b>Sub-menu:</b> <code>/ip proxy direct</code></p>
 
<p>
 
<p>
 +
If <b>parent-proxy</b> property is specified, it is possible to tell proxy server whether to try to pass the request to the parent proxy or to resolve it connecting to the requested server directly. Direct Access List is managed just like Proxy Access List described in the previous chapter except the action argument.
 +
</p>
 +
<p>
 +
Unlike the access list, the direct proxy access list has default action equal to deny. It takes place when no rules are specified or a particular request did not match any rule.
 
</p>
 
</p>
 +
<table class="styled_table">
 +
<tr>
 +
  <th width="40%">Property</th>
 +
  <th >Description</th>
 +
</tr>
 +
<tr>
 +
    <td><var><b>a</b></var> (<em></em>; Default: <b></b>)</td>
 +
    <td></td>
 +
</tr>
 +
</table>
  
 
<h2>Cache Management</h2>
 
<h2>Cache Management</h2>
 
<p><b>Sub-menu:</b> <code>/ip proxy cache</code></p>
 
<p><b>Sub-menu:</b> <code>/ip proxy cache</code></p>
 
<p>
 
<p>
 +
Cache access list specifies, which requests (domains, servers, pages) have to be cached locally by web proxy, and which not. This list is implemented exactly the same way as web proxy access list. Default action is to cache object (if no matching rule is found).
 
</p>
 
</p>
 +
<table class="styled_table">
 +
<tr>
 +
  <th width="40%">Property</th>
 +
  <th >Description</th>
 +
</tr>
 +
<tr>
 +
    <td><var><b>a</b></var> (<em></em>; Default: <b></b>)</td>
 +
    <td></td>
 +
</tr>
 +
</table>
  
 
<h2>Connections</h2>
 
<h2>Connections</h2>
 
<p><b>Sub-menu:</b> <code>/ip proxy connections</code></p>
 
<p><b>Sub-menu:</b> <code>/ip proxy connections</code></p>
 
<p>
 
<p>
 +
This menu conntains the list of current connections the proxy is serving.
 
</p>
 
</p>
 +
<table class="styled_table">
 +
<tr>
 +
  <th width="40%">Property</th>
 +
  <th >Description</th>
 +
</tr>
 +
<tr>
 +
    <td><var><b>a</b></var> (<em></em>; Default: <b></b>)</td>
 +
    <td></td>
 +
</tr>
 +
</table>
  
 
<h2>Cache Inserts</h2>
 
<h2>Cache Inserts</h2>
 
<p><b>Sub-menu:</b> <code>/ip proxy inserts</code></p>
 
<p><b>Sub-menu:</b> <code>/ip proxy inserts</code></p>
 
<p>
 
<p>
 +
This menu shows statistics on objects stored in cache (cache inserts).
 
</p>
 
</p>
 +
<table class="styled_table">
 +
<tr>
 +
  <th width="40%">Property</th>
 +
  <th >Description</th>
 +
</tr>
 +
<tr>
 +
    <td><var><b>a</b></var> (<em></em>; Default: <b></b>)</td>
 +
    <td></td>
 +
</tr>
 +
</table>
  
 
<h2>Cache Lookups</h2>
 
<h2>Cache Lookups</h2>
 
<p><b>Sub-menu:</b> <code>/ip proxy inserts</code></p>
 
<p><b>Sub-menu:</b> <code>/ip proxy inserts</code></p>
 
<p>
 
<p>
 +
This menu shows statistics on objects read from cache (cache lookups).
 
</p>
 
</p>
 +
<table class="styled_table">
 +
<tr>
 +
  <th width="40%">Property</th>
 +
  <th >Description</th>
 +
</tr>
 +
<tr>
 +
    <td><var><b>a</b></var> (<em></em>; Default: <b></b>)</td>
 +
    <td></td>
 +
</tr>
 +
</table>
  
 
<h2>HTTP Methods</h2>
 
<h2>HTTP Methods</h2>

Revision as of 13:44, 12 November 2009

Version.png

Applies to RouterOS: v3, v4

Summary

Sub-menu: /ip proxy

Standards: RFC 1945, RFC 2616


This service performs proxying of HTTP and HTTP-proxy (for FTP, HTTP and HTTPS protocols) requests. Web proxy performs Internet object cache function by storing requested Internet objects, i.e., data available via HTTP and FTP protocols on a system positioned closer to the recipient than the site the data is originated from. Here 'closer' means increased path reliability, speed or both. Web browsers can then use the local proxy cache to speed up access and reduce bandwidth consumption. When setting up proxy service, make sure it serves only your clients, and is not misused as relay. Please read the security notice in the Access List Section! Note that it may be useful to have Web proxy running even with no cache when you want to use it only as something like HTTP and FTP firewall (for example, denying access to mp3 files) or to redirect requests to external proxy (possibly, to a proxy with caching functions) transparently.

General

Sub-menu: /ip proxy

Property Description
always-from-cache (yes | no; Default: no)
cache-administrator (string; Default: webmaster) Administrator's e-mail displayed on proxy error page
cache-hit-dscp (integer: 0..63; Default: 4)
cache-on-disk (yes | no; Default: no)
max-cache-size (none | unlimited | integer: 0..4294967295; Default: none) Specifies the maximal cache size, measured in kibibytes
max-client-connections (integer: 1..5000; Default: 600) Maximal number of connections accepted from clients (any further connections will be rejected)
max-fresh-time (time; Default: 3d) Maximal time to store a cached object. The validity period of an object is is usually defined by the object itself, but in case it is set too high, you can override the maximal value
max-server-connections (integer: 1..5000; Default: 600) Maximal number of connections made to servers (any further connections from clients will be put on hold until some server connections will terminate)
parent-proxy (IP; Default: 0.0.0.0) IP address and port of another HTTP proxy to redirect all requests to. If set to 0.0.0.0 parent proxy is not used.
parent-proxy-port (integer: 0..65535; Default: 0) Port that parent proxy is listening on.
port (integer: 0..65535; Default: 8080) TCP port the proxy server will be listening on. This port have to be specified on all clients that want to use the server as HTTP proxy. Transparent (with zero configuration for clients) proxy setup can be made by redirecting HTTP requests to this port in IP firewall using destination NAT feature
serialize-connections (yes | no; Default: no)
src-address (IP; Default: 0.0.0.0) Proxy will use specified address when connecting to parent proxy or web site. If set to 0.0.0.0 then appropriate IP address will be taken from routing table.

Menu Specific commands

Example

To enable the proxy on port 8000:

[admin@MikroTik] ip proxy> set enabled=yes port=8000
[admin@MikroTik] ip proxy> print
                     enabled: yes
                 src-address: 0.0.0.0
                        port: 8000
                parent-proxy: 0.0.0.0:0
                 cache-drive: system
         cache-administrator: "dmitry@mikrotik.com"
         max-disk-cache-size: none
          max-ram-cache-size: 100000KiB
          cache-only-on-disk: yes
  maximal-client-connections: 1000
  maximal-server-connections: 1000
             max-object-size: 2000KiB
              max-fresh-time: 3d
[admin@MikroTik] ip proxy>

Remember to secure your proxy by preventing unauthorized access to it, otherwise it may be used as an open proxy. Also you need to setup destination NAT in order to utilize transparent proxying facility:

[admin@MikroTik] ip firewall nat> add chain=dstnat protocol=tcp dst-port=80 action=redirect to-ports=8000
[admin@MikroTik] ip firewall nat> print
Flags: X - disabled, I - invalid, D - dynamic
 0   chain=dstnat protocol=tcp dst-port=80 action=redirect to-ports=8000
[admin@MikroTik] ip firewall nat>

Access List

Sub-menu: /ip proxy access

Access list is configured like a regular firewall rules. Rules are processed from the top to the bottom. First matching rule specifies decision of what to do with this connection. There is a total of 6 classifiers that specify matching constraints. If none of these classifiers is specified, the particular rule will match every connection. If connection is matched by a rule, action property of this rule specifies whether connection will be allowed or not. If the particular connection does not match any rule, it will be allowed.

Property Description
a (; Default: )


Direct Access

Sub-menu: /ip proxy direct

If parent-proxy property is specified, it is possible to tell proxy server whether to try to pass the request to the parent proxy or to resolve it connecting to the requested server directly. Direct Access List is managed just like Proxy Access List described in the previous chapter except the action argument.

Unlike the access list, the direct proxy access list has default action equal to deny. It takes place when no rules are specified or a particular request did not match any rule.

Property Description
a (; Default: )

Cache Management

Sub-menu: /ip proxy cache

Cache access list specifies, which requests (domains, servers, pages) have to be cached locally by web proxy, and which not. This list is implemented exactly the same way as web proxy access list. Default action is to cache object (if no matching rule is found).

Property Description
a (; Default: )

Connections

Sub-menu: /ip proxy connections

This menu conntains the list of current connections the proxy is serving.

Property Description
a (; Default: )

Cache Inserts

Sub-menu: /ip proxy inserts

This menu shows statistics on objects stored in cache (cache inserts).

Property Description
a (; Default: )

Cache Lookups

Sub-menu: /ip proxy inserts

This menu shows statistics on objects read from cache (cache lookups).

Property Description
a (; Default: )

HTTP Methods

Options

This method is a request of information about the communication options available on the chain between the client and the server identified by the Request-URI. The method allows the client to determine the options and (or) the requirements associated with a resource without initiating any resource retrieval

GET

This method retrieves whatever information identified by the Request-URI. If the Request-URI refers to a data processing process than the response to the GET method should contain data produced by the process, not the source code of the process procedure(-s), unless the source is the result of the process.

The GET method can become a conditional GET if the request message includes an If-Modified-Since, If-Unmodified-Since, If-Match, If-None-Match, or If-Range header field. The conditional GET method is used to reduce the network traffic specifying that the transfer of the entity should occur only under circumstances described by conditional header field(-s).

The GET method can become a partial GET if the request message includes a Range header field. The partial GET method intends to reduce unnecessary network usage by requesting only parts of entities without transferring data already held by client.

The response to a GET request is cacheable if and only if it meets the requirements for HTTP caching.

HEAD

This method shares all features of GET method except that the server must not return a message-body in the response. This retrieves the metainformation of the entity implied by the request which leads to a wide usage of it for testing hypertext links for validity, accessibility, and recent modification.

The response to a HEAD request may be cacheable in the way that the information contained in the response may be used to update previously cached entity identified by that Request-URI.

POST

This method requests that the origin server accept the entity enclosed in the request as a new subordinate of the resource identified by the Request-URI.

The actual action performed by the POST method is determined by the origin server and usually is Request-URI dependent.

Responses to POST method are not cacheable, unless the response includes appropriate Cache-Control or Expires header fields.

PUT

This method requests that the enclosed entity be stored under the supplied Request-URI. If another entity exists under specified Request-URI, the enclosed entity should be considered as updated (newer) version of that residing on the origin server. If the Request-URI is not pointing to an existing resource, the origin server should create a resource with that URI.

If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries should be treated as stale. Responses to this method are not cacheable.

TRACE

This method invokes a remote, application-layer loop-back of the request message. The final recipient of the request should reflect the message received back to the client as the entity-body of a 200 (OK) response. The final recipient is either the origin server or the first proxy or gateway to receive a Max-Forwards value of 0 in the request. A TRACE request must not include an entity.

Responses to this method MUST NOT be cached.


[Back to Content]