10 ms·
Sure. All the proxies between you and the client are a lot more likely to cache a GET than a POST.
by fusiongyro 14y ago
Sure. All the proxies between you and the client are a lot more likely to cache a GET than a POST.
- mistercow 14y agoI've never looked at the code for caching GET requests, but I am going to go out on a limb and say that that code is probably not optimized for keying on 1KB URLs. In fact, caching seems like a really good consideration regarding the original point about 1KB being too big for a GET request in terms of architecture design.
- fusiongyro 14y agoYou're really going to continue the debate by basically saying "I haven't read the code but it must not work like that?" In Squid it's 4K by default: http://www.squid-cache.org/mail-archive/squid-users/200208/0423.html http://www.squid-cache.org/mail-archive/squid-users/200208/0... I see no reference to a maximum URL size in Varnish, and a cursory glance through the source code is not revealing a hard-coded size. I'm not shocked. PHK is well-known for writing good code and good code generally doesn't have a lot of magic numbers. I really can't stand contrafactual arguing from first principles. I gave you a legitimate non-aesthetic reason and you came back with a softly wilted notion conjured whole out of your imagination. Shut up already.