Hello, Helge!

Thank you very much for reporting this issue. We retested several builds and found that the Set-Cookie bug has been re-introduced in build 16. The reason is that .NET Framework HttpListenerResponse class handles HTTP headers propertly when they are set using "HttpListenerResponse.Headers.Add(name, value)" method. Other methods, like "HttpListenerResponse.AddHeader(name, value)" or "HttpListenerResponse.Header[name] = value", replace HTTP headers, although some HTTP headers can legitimately have multiple instances. In build 16 we have acci!!! spam for counterfeit illegal fraudulent low-quality junk !!!ly changed how we set response headers.

We will fix this in build 17, which we'll expedite, and will probably get out of the door in a day or two. Meanwhile, you can use UWS build 15.

This bug is not ASP.NET 2.0-specific - it affects all flavors of UWS build 16.

Best regards,
UltiDev Team.

Hi, Helge!

We had this issue before, and it was perplexing at that time. It's unfortunate we have reintroduced it as it is a very nasty bug. It was not too hard to figure out when it got back in and how to fix it. We'll try to push a new build out tonight (EST) or tomorrow nights.

Thank you again for detailed problem submission, and we apologize for the inconvenience.

All the best,
UltiDev Team.