3 ms·
It all boils down to the server/client. as in: does it matter if the http spec says X if the most used browser only sends X/2? back in 90-something i had to re
by gcb0 14y ago
It all boils down to the server/client. as in: does it matter if the http spec says X if the most used browser only sends X/2?
back in 90-something i had to research that for url and cookies.
msdn specs said something like
"[url|cookies] should be at least [some size]"
mozilla's and w3c specs said:
"[url|cookies] should be at most [some size]"
for everything. url lenght. cookie lenght. number of cookies per domain. number of cookies per subdomain... it was like that for ALL items. one said 'at least' the other 'at most', and for added fun, all the values where exactly the same on both.
- jacques_chester 14y agoThe thing is that the RFCs use MAY and SHOULD for these things. Not MUST or SHALL. So it's implementation-defined from the get-go. I presume that the people writing HTTP servers and clients usually found it easier to allocate a fixed-length char array.
- gcb0 14y agoMay vs Should i can take. but At least vs At most I sincerely can't.