DotNetNewsgroup.com  
web access to complete list of Microsoft.NET newsgroups
   home   |   control panel login   |   archive  |  
 
  carried group
academic
adonet
aspnet
aspnet.announcements
aspnet.buildingcontrols
aspnet.caching
aspnet.datagridcontrol
aspnet.mobile
aspnet.security
aspnet.webcontrols
aspnet.webservices
assignment_manager
datatools
dotnet.distributed_apps
dotnet.general
dotnet.myservices
dotnet.nternationalization
dotnet.scripting
dotnet.security
dotnet.vjsharp
dotnet.vsa
dotnet.xml
dotnetfaqs
framework
framework.clr
framework.compactframework
framework.component_services
framework.controls
framework.databinding
framework.drawing
framework.enhancements
framework.interop
framework.odbcnet
framework.performance
framework.remoting
framework.sdk
framework.setup
framework.webservices
framework.windowsforms
framework.wmi
frwk.windowsforms.designtime
lang.csharp
lang.jscript
lang.vb
lang.vb.controls
lang.vb.data
lang.vb.upgrade
lang.vc
lang.vc.libraries
  
 
start date: Sun, 12 Aug 2007 11:13:00 +0300,    posted on: microsoft.public.dotnet.framework        back       

Thread Index
  1    dav dave
          2    UL-Tomten


cookie contanier does not correctly parse Set-Cookie header with domain token   
(sorry early post sent before finished...)

hi,

i am using HttpWebRequest with cookie container to perform web request.
HttpWebRequest req = (HttpWebRequest)WebRequest.Create(uri);

the cookies are parsed correcly for Set-Cookie header like this:
Set-Cookie: id=123123;
and it can be retrived with the lime:
m_cookies.GetCookieHeader(uri);

if the set cookie header includes a domain entry, like the following line:
Set-Cookie: id=123123; domain=www.domain.com; path=/

the cookie header is not parsed correctly (the domain is the same as the Uri 
for the web request).
and the line:
m_cookies.GetCookieHeader(uri);

returns empty string.

please help this is urgent and if there is no mistake on my side, this is a 
bug!

thanks.
Date:Sun, 12 Aug 2007 11:13:00 +0300   Author:  

Re: cookie contanier does not correctly parse Set-Cookie header with domain token   
On Aug 12, 10:13 am, "dav" <dave> wrote:


> (sorry early post sent before finished...)


No problem. It's easy to get carried away.


> if the set cookie header includes a domain entry, like the following line:
> Set-Cookie: id=123123; domain=www.domain.com;path=/
> the cookie header is not parsed correctly [...]


According to RFC 2109, the above cookie should be rejected, since it
doesn't start with a dot:

4.2.2 Set-cookie syntax

Domain=domain
      Optional.  The Domain attribute specifies the domain for which
the
      cookie is valid.  An explicitly specified domain must always
start
      with a dot.

Could this be the problem?
Date:Sun, 12 Aug 2007 10:42:58 -0700   Author:  

Google
 
Web dotnetnewsgroup.com


COPYRIGHT ?2005, EUROFRONT WORLDWIDE LTD., ALL RIGHT RESERVE  |   Contact us