Proxy's "cache-on-disk: yes" do not work

RouterOS Virtualization
1

Problem: mikrotik don’t want to save cache files in Proxy server on his ROM(30GB). But he successfully save on his RAM(when cache-on-disk: no) that is 1GB

Scenario:
CHR config is almost clean, just default gateway and enabled proxy.

I use KVM on CentOS 7:
[root@TOTORO ~]# rpm -qa |grep qemu

qemu-guest-agent-2.3.0-4.el7.x86_64
qemu-kvm-1.5.3-105.el7_2.4.x86_64
libvirt-daemon-driver-qemu-1.2.17-13.el7_2.4.x86_64
qemu-img-1.5.3-105.el7_2.4.x86_64
qemu-kvm-common-1.5.3-105.el7_2.4.x86_64
ipxe-roms-qemu-20130517-8.gitc4bce43.el7_2.1.noarch

[admin@MikroTik] > system resource print

                   uptime: 1h5m41s
                  version: 6.34.6 (bugfix)
               build-time: Jun/06/2016 08:37:27
              free-memory: 627.6MiB
             total-memory: 1001.0MiB
                      cpu: Intel
                cpu-count: 1
            cpu-frequency: 3411MHz
                 cpu-load: 1%
           free-hdd-space: 29.8GiB
          total-hdd-space: 29.9GiB
  write-sect-since-reboot: 640
         write-sect-total: 641
        architecture-name: x86_64
               board-name: CHR
                 platform: MikroTik

[admin@MikroTik] > ip proxy print

                 enabled: yes
             src-address: ::
                    port: 8080
               anonymous: yes
            parent-proxy: ::
       parent-proxy-port: 0
     cache-administrator: 
          max-cache-size: unlimited
   max-cache-object-size: 504800KiB
           cache-on-disk: yes
  max-client-connections: 600
  max-server-connections: 600
          max-fresh-time: 3d
   serialize-connections: no
       always-from-cache: no
          cache-hit-dscp: 4
              cache-path: web-proxy
2

I found the solution.
My problem is very old bug from version 4.

You must put the same name for cache-administrator and cache-path:

[admin@MikroTik] > ip proxy print        
                 enabled: yes
             src-address: ::
                    port: 8080
               anonymous: yes
            parent-proxy: ::
       parent-proxy-port: 0
cache-administrator: web-proxy
max-cache-size: unlimited
   max-cache-object-size: 504800KiB
           cache-on-disk: yes
  max-client-connections: 600
  max-server-connections: 600
          max-fresh-time: 3d
   serialize-connections: no
       always-from-cache: no
          cache-hit-dscp: 4
cache-path: web-proxy
3

So that’s all? Nobody care that there is bug and it will not be fixed?

4

Probably nobody cares anymore, proxy server with cache is mostly a thing of the past.