"always-from-cache" documentation ?

Hi,

what is these parameters ?

       serialize-connections: no
       always-from-cache: no



[admin@MikroTik] /ip proxy> print 
                 enabled: yes
             src-address: 0.0.0.0
                    port: 8080
            parent-proxy: 0.0.0.0
       parent-proxy-port: 0
             cache-drive: system
     cache-administrator: "webmaster"
          max-cache-size: 973000KiB
           cache-on-disk: yes
  max-client-connections: 1000
  max-server-connections: 1000
          max-fresh-time: 3d
[b]   serialize-connections: no
       always-from-cache: no[/b]
          cache-hit-dscp: 4

Is there none to answer this?!! come on man waiting for the answer..

From the manual.. http://www.mikrotik.com/testdocs/ros/3.0/pnp/proxy.php

serialize-connections (yes | no; default: no) - Do not make multiple connections to server for multiple client connections, if possible (i.e. server supports persistent HTTP connections). Clients will be served on FIFO principle; next client is processed when response transfer to the previous one is completed. If a client is idle for too long (max 5 seconds by default), it will give up waiting and open another connection to the server

always-from-cache (yes | no; default: no) - ignore client refresh requests if the content is
considered fresh

-Gerard

always-from-cache is wonderful actually but i wonder if it obeys the rules for like webmail systems like gmail or yahoo mail so as not to load stale content. (old)

Doesn’t the proxy know that this is actually a refresh request? When a clients makes a refresh request with pressing F5 while in his web browser?