Tldr: I used wireshark to dig into the requests and saw multiple requests for the same file. I figured this might be buggy behavior. Where's the cache?

Background: Ive been using nginx through privoxy as an alternative to secondlifes caching because 20GB can fill on just driving through 4 sims, presuming you actually wanted to look around in each of them. Anyways... I noticed repeat requests and figured maybe I was mis-serving things to the viewer and causing problems. Then, I got wireshark and tried without my proxy/cache, just the viewers native one.

Issue: Assuming i can read these logs (debatable)... it appears the same files are being http-requested multiple times even when they should be served from cache (as in, there is room and there has been time since last request for it to get saved.

While I do have a 20 minute wireshark capture, its 500MB so I found one texture that was re-downloaded 13 times within that 20 minutes and I'm giving that as an example. This particular texture seems to be someones jacket, so no jumpscares.

The image attached shows a search was for "Range: bytes" which is showing the Range request bytes and Content-Range response bytes, so you can see what requests were made, and what was served. The viewer is requesting upper ranges of null, 180631, 704919, and 2802071 (I want to guess these are relevant to discard levels). It even once asked for 98181-2802071 which is outside of the range of the file. This is why I'm most suspicious of an issue, because asking for byte 98181 in a 98182 byte long file is asking for the last byte of the file, plus more - which it should know doesn't exist. So, the server rightfully gives it 1 byte and reminds the viewer that the file is 98192 long. Unless that one byte was being used for a check, it seems odd to knowingly request it - so as a programmer I want to guess there's a one-by-one error somewhere.

Sorry for being rant-ey but I don't know enough about general network diagnostics in order to give this information in a clear and concise manner.