CookieContainer domain handling issue - by SalarSoft

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 478521 Comments
Status Closed Workarounds
Type Bug Repros 8
Opened 7/30/2009 5:55:41 AM
Access Restriction Public


It is really confusing how CookieContainer handles domain.
According to RFC 2109 when we set a cookie to domain "" the CookieContainer does not send the cookie to the domain.
Receiving the cookie from and both are expected. But nothing will be sent!

I believe it is a bug!

I have searched a lot about this issue and I found some hacks to pass through this, but still it don't work properly:

People discuss:
Sign in to post a comment.
Posted by bdunlay on 9/11/2013 at 11:19 AM
This exact issue is still present in Silverlight 5.
Posted by a_11 on 3/11/2010 at 4:24 AM
I added another feedback about backport this issue to .NET 2.0-3.5
If anybody interested as well you can vote for it
Posted by a_11 on 3/11/2010 at 4:17 AM
since this is a bug (according to RFC) and not a NEW feature I think it is still need to be back ported, because this issue is really annoying.
Posted by schneipp on 10/16/2009 at 6:57 AM
So basically we need to buy VisualStudio 2010 when we want to offer our customers a fixed CookieContainer?
Posted by David [MSFT] on 8/10/2009 at 12:31 PM
Due to the complexity, there are no plans to backport this fix into .NET 2.0/3.0/3.5.

Thank you,

Network Class Library Team
Posted by SalarSoft on 7/31/2009 at 12:04 PM
Thanks for the fast fix!
Will be there a hot-fix or service pack for .NET 2.0 about this issue?
Posted by Microsoft on 7/31/2009 at 9:20 AM
Thanks for reporting this issue. We fixed the problem in our code base and the fix will be included in .NET 4.0 Beta 2.
Posted by Microsoft on 7/31/2009 at 12:15 AM
Thanks for your feedback.

We were able to reproduce the issue you are seeing. We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.