why a hard (force) refresh cache (ctrf + f5) is needed?

[furyNerd]

hi, i start a server to access localnet sites, by:

proxy --hostname 0.0.0.0 --port 8899 --basic-auth username:password

most time it works ok, but i found i need to do a hard/foce refresh cache (ctrl+f5) on my client browser when access some sites (i guess these sites are on the same server/ip with differents ports)

e.g., if i just visited site a and wish to visit site b, i input the site b url in browser and hit enter, the page shows content from site a, and i need to do the ctrl+f5 on that page, input the site b url again, then site b is able to access.

but if i want to again visit some new site a's links, i need hard refresh site a's url again...why a hard (force) refresh cache (ctrf + f5) is needed?

is there any suggestion about this?
all i can found is some logs as follows, where the 302 code looks suspicious

2024-11-15 15:20:46,360 - pid:61001 [I] plugins.load:89 - Loaded plugin proxy.http.proxy.HttpProxyPlugin
2024-11-15 15:20:46,361 - pid:61001 [I] plugins.load:89 - Loaded plugin proxy.http.proxy.auth.AuthPlugin
2024-11-15 15:20:57,757 - pid:61006 [I] server.access_log:388 - 192.168.1.103:51024 - GET local.site.a.com:80/ - 302  - 546 bytes - 6887.95ms
2024-11-15 15:20:57,956 - pid:61015 [I] server.access_log:388 - 192.168.1.103:51028 - GET local.site.a.com:80/rest/api/2/filter/46122?expand=subscriptions[-5:]&_=1731655251183 - 200  - 1186 bytes - 5952.16ms
2024-11-15 15:20:57,989 - pid:61011 [I] server.access_log:388 - 192.168.1.103:51030 - GET local.site.a.com:80/rest/scriptrunner/latest/sr-analytics?origReferrer=&parentLocation=http%3A%2F%2Flocal.site.a.com%2Fissues%2F%3Ffilter%3D46122 - 200  - 644 bytes - 5960.98ms
2024-11-15 15:21:08,746 - pid:61004 [I] server.access_log:388 - 192.168.1.103:51029 - GET local.site.a.com:80/rest/menu/latest/appswitcher?_=1731655251184 - 200  - 795 bytes - 16716.86ms
2024-11-15 15:21:08,898 - pid:61010 [I] server.access_log:388 - 192.168.1.103:51027 - POST local.site.a.com:80/rest/issueNav/latest/preferredSearchLayout - 200  - 643 bytes - 16893.90ms
2024-11-15 15:21:13,663 - pid:61004 [I] server.access_log:388 - 192.168.1.103:51034 - POST local.site.b.com:80/plugins/servlet/gadgets/dashboard-diagnostics - 422 Unprocessable Entity - 3394 bytes - 15654.08ms

update: i tried tinyproxy on server, looks no such case...