> So, giving people the correct file instead of making them know what they need (which many people dont... especially if it is browser specific) is not a good r

> So, giving people the correct file instead of making them know what they need (which many people dont... especially if it is browser specific) is not a good reason? No, it is not. Give the user the option of what to download. What if I want the Windows version even though I'm running Linux? > What if a server wants to provide a client with native order endianess (for RPC for example), that shouldnt be allowed? RPC should have a standard byte order defined. > Tell that to my browser which countless times doesnt fetch a new file because it has a cached copy. That's based on cache control, which isn't affected by the Date header sent by the server. > Often times, the server isnt a single server, but rather a set of load-balanced servers. I know. I've set these systems up before. There shouldn't be anything of consequence stored on the client. So what if someone changes the session ID? Does it really matter? If someone has someone else's ID they probably have the signature too. If it's a random search, using random ids goes a very long way. Also, beyond sessions, there doesn't need to be a session. There are now ways to store data on the client that don't require sending it back and forth to the server on every request.