Comments in-line.
Marc Saegesser
> -Original Message-
> From: dIon Gillard [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, March 07, 2002 6:08 PM
> To: Jakarta Commons Developers List
> Subject: Re: [httpclient] Constructing Cookies with null
> domains (again)
>
Marc Saegesser wrote:
>/* I think this should throw IAE, but I can live with it,
> * if people really think this sort of thing is useful.
> */
>cookies[0] = new Cookie(null, "name0", "value0");
>
It's not that we think it's useful - it's being done now, so changing it
breaks people's code.
>/*
e header until someone comes along and calls the
setDomain() and setPath() methods on them to give them a valid values.
Marc Saegesser
> -Original Message-
> From: dIon Gillard [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 06, 2002 10:05 PM
> To: Jakarta Commons Develope
Marc Saegesser wrote:
>Well, I don't see your cookie dump, but what your going to see on the server
>side (since you're running in a servlet) is different than what the client
>is going to see (which is what HttpClient is).
>
>Let me see if I can beat this to death one more time. HttpClient can
r from manually creating a cookie with a domain of .com
and manually adding that to the HttpState.
Marc Saegesser
> -Original Message-
> From: Scott Rogers [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 06, 2002 2:49 PM
> To: Jakarta Commons Developers List
> Subject: R
ques#\n");
return sb.toString();
}
- Original Message -
From: "Marc Saegesser" <[EMAIL PROTECTED]>
To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, March 06, 2002 2:22 PM
Subject: RE: [httpclient] Constr
March 06, 2002 6:59 PM
> To: Jakarta Commons Developers List
> Subject: Re: [httpclient] Constructing Cookies with null
> domains (again)
>
>
> Marc Saegesser wrote:
>
> >I've spent a fair amount of time recently reading and
> re-reading RFC 2109
> &g
Marc Saegesser wrote:
>I've spent a fair amount of time recently reading and re-reading RFC 2109
>and the Netscape cookie spec-like-thing. Here's my current understanding.
>
>All cookies have a domain. A domain is required in order to determine which
>cookies should be sent with a given request
'
> Subject: RE: [httpclient] Constructing Cookies with null
> domains (again)
>
>
> I think both Marc and dIon raise some good points. The spec
> clearly allows
> domain to be null in a Set-Cookie header, but also speaks to
> what clients
> should assume to be the
I think both Marc and dIon raise some good points. The spec clearly allows
domain to be null in a Set-Cookie header, but also speaks to what clients
should assume to be the domain in that circumstance.
So what is a *.httpclient.Cookie, really? A representation of the somewhate
abstract "client
Marc Saegesser wrote:
>There was some discussion last month about the expected results of
>constructing a Cookie with a null domain. I can't find the exact email
>where the decision was reached, but I think the concensus was that we should
>support a null domain and default to the request host.
11 matches
Mail list logo
