--- Nigel Wetters <[EMAIL PROTECTED]> wrote: > One of our partners ran into a problem with load balancing on IIS. Each server set a >session > cookie, which eventually pushed the useful cookies out of the browser's store. Yet >another > reason why IIS isn't ready for enterprise-level solutions. While I definitely have some issues with IIS, this isn't one of them. There is a domain limit to cookies (20, I think) and a total limit (300, as I recall) that a browser is required to store, according to standards. While the browser may exceed those limits, it is in no way required to do so. If a particular site or application is having problems with too many cookies, it's due to that site or domain poorly managing cookies and setting too many of them, not the necessarily the Web server. IIS does not set the cookies, so it's not to blame. ASP might set them, with its session managing tools, but that's still a configuration or programming issue and not a problem with IIS. As for my issues with IIS, I am sick of having to switch to NPH scripts because it mangles headers when setting cookies and doing a simultaneous redirect. This bug has been in IIS for the LAST 3 VERSIONS!!! You would think that MS would get it right after a while... Cheers, Curtis Poe ===== Senior Programmer Onsite! Technology (http://www.onsitetech.com/) "Ovid" on http://www.perlmonks.org/ __________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
