CookieContainer subdomain handling issue in .NET 4.0 - by i1yich

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 771651 Comments
Status Closed Workarounds
Type Bug Repros 6
Opened 11/19/2012 2:08:55 PM
Access Restriction Public


After fixing famous bug in CookieContainer about leading dot in hostname (FeedbackID=478521, also described in, there is a new bug, that came to replace old one.

Now, when you're setting RFC2109-cookie (Version=1) for parent domain "", you cannot get it back for subdomain "".

See attached project for more tests reproducing the problem.
Sign in to post a comment.
Posted by Tommaso Scalici on 3/7/2015 at 2:32 PM
.NET Framework 4.6 and Windows 10 are about to get released, and this is still not fixed.
This bug is really annoying.
Posted by David [MSFT] on 7/23/2014 at 4:13 PM
Thank you for your feedback.

We are considering fixing this bug for a future version of the .NET Framework.

Networking Team (david)
Posted by Sunday Ironfoot on 2/20/2014 at 7:24 AM
"Regrettfully, we are unable to take this bug at this time"

Any reason why? This bug is really affecting us.
Posted by Microsoft on 4/5/2013 at 3:20 PM
Regrettfully, we are unable to take this bug at this time
Posted by Microsoft on 11/19/2012 at 10:10 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been reproduced and has been routed to the appropriate VS development team for review. We will contact you if we require any additional information.
Posted by Microsoft on 11/19/2012 at 2:52 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(