URL...
But thanks for the http-client anyway it's a very good thing!
Ciao,
Robert.
-Original Message-
From: Oleg Kalnichevski [mailto:@bearingpoint.com]
Sent: 21 September 2004 15:36
To: [EMAIL PROTECTED]
Subject: Re: Cookie problems / strict mode
Robert,
It is a known problem wit
/redirects.html
(3) Override HttpMethodBase#addCookieRequestHeader() method
protected void addCookieRequestHeader(
HttpState state, HttpConnection conn)
throws IOException, HttpException {
// Clean up the cookie headers
removeRequestHeader("cookie");
CookieSp
strict mode, but at the same time it accepts just the
cookies send in a single line.
I saw a patch from 2003 which allowed the user to add a cookie
request-header manually. This patch has been removed again from the new
version? Is there now another technique for that? I don't understand why
gzilla/show_bug.cgi?id=31163
DateParser refactoring; Stateful cookie specs
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RE
gzilla/show_bug.cgi?id=31163
DateParser refactoring; Stateful cookie specs
[EMAIL PROTECTED] changed:
What|Removed |Added
OtherBugsDependingO||31211
gzilla/show_bug.cgi?id=31163
DateParser refactoring; Stateful cookie specs
--- Additional Comments From [EMAIL PROTECTED] 2004-09-14 08:51 ---
Created an attachment (id=12725)
Patch (take 2)
-
To unsubscribe, e-mail:
gzilla/show_bug.cgi?id=31163
DateParser refactoring; Stateful cookie specs
--- Additional Comments From [EMAIL PROTECTED] 2004-09-14 08:50 ---
Sorry. My oversight. It was not my intention to remove the
DateParser#parseDate(String) method.
New patch restores the DateParser.parseDate(Strin
gzilla/show_bug.cgi?id=31163
DateParser refactoring; Stateful cookie specs
--- Additional Comments From [EMAIL PROTECTED] 2004-09-14 02:13 ---
Hi Oleg,
I think we should leave DateParser.parseDate(String), and just have it use the default
list of patterns.
Other than that it looks prett
gzilla/show_bug.cgi?id=31163
DateParser refactoring; Stateful cookie specs
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
gzilla/show_bug.cgi?id=31163
DateParser refactoring; Stateful cookie specs
--- Additional Comments From [EMAIL PROTECTED] 2004-09-10 14:25 ---
Created an attachment (id=12694)
Patch (take 1)
-
To unsubscribe, e-mail:
gzilla/show_bug.cgi?id=31163
DateParser refactoring; Stateful cookie specs
Summary: DateParser refactoring; Stateful cookie specs
Product: Commons
Version: Nightly Builds
Platform: Other
OS/Version: Other
Status: NEW
Severity:
Kalnichevski [mailto:[EMAIL PROTECTED]
Sent: Monday, August 23, 2004 3:54 PM
To: Commons HttpClient Project
Subject: Re: Set-Cookie: filtering on the path= verses URL path
Steve,
The cookie with the path attribute "/insight" may certainly not be sent
to a url starting with "/insigh
Steve,
The cookie with the path attribute "/insight" may certainly not be sent
to a url starting with "/insightreporting". So, HttpClient's behavior is
correct.
You can pursue one of three options to work the problem around.
(1) If you do not mind using ALPHA softwa
Hi All,
We have a URL that works in IE and Netscape, but the cookie is not getting sent
from HTTPClient.
Here is the URL and the Set-Cookie
https://was4.hewitt.com/insightreporting/reports/websitemonitoring
<https://was4.hewitt.com/insightreporting/reports/websitemonitoring>
re
org/dist/jakarta/commons/httpclient/RELEASE-NOTES
-2.0.txt>.
Mike
On Aug 4, 2004, at 11:26 AM, Doug wrote:
The release notes
(http://www.apache.org/dist/jakarta/commons/httpclient/RELEASE-NOTES)
say:
-
(4) Cookie management
* 'Ignore cookies' cookie policy
-
But I&#x
The release notes
(http://www.apache.org/dist/jakarta/commons/httpclient/RELEASE-NOTES) say:
-
(4) Cookie management
* 'Ignore cookies' cookie policy
-
But I'm not finding this capability in the docs or source code. Am I
just missing s
client = new HttpClient();
HttpState hs = client.getState();
hs.addCookie(new Cookie("search.msn.fr", "smc_classic",
"df=0&af=0&rc=50&nw=0&sc=&rs=1", "/", d, false));
hs.addCookie(new Cookie("sear
();
hs.addCookie(new Cookie("search.msn.fr", "smc_classic",
"df=0&af=0&rc=50&nw=0&sc=&rs=1", "/", d, false));
hs.addCookie(new Cookie("search.msn.fr", "smc_g",
"v=1&pvs=classic&ssp=1&df=1", &
Thank you Mike.
But after a long reflexion, I've found that I've not taken the good part
of the problem.
In fact, what I want to do is to send a Cookie in the headers of my
first requested page, no matter the cooklies sets by the server.
How to do that ?
Mathias
PS: my english is
Hi Mathias,
The best way is to just create a new instance of Cookie, copying the
values you want to keep, and add it to the HttpState.
Mike
On Jul 30, 2004, at 3:09 AM, Mathias Cianci wrote:
Hello everybody,
Is it possible with httpclient to change the value of a specific
variable sent in a
Hello everybody,
Is it possible with httpclient to change the value of a specific
variable sent in a cookie by a server.
For example, when the server send the cookie var1=5&*var2=7*&var3=4, I
want to save the cookie var1=5&*var2=174*&var3=4
Thank you for advance,
Mathias
An
gzilla/show_bug.cgi?id=19102
Set-Cookie2 and Set-Cookie
[EMAIL PROTECTED] changed:
What|Removed |Added
Target Milestone|3.0 Final
Duzayak,
'Set-Cookie' (request) header is not the same thing as the 'Cookie' (response) header.
CookieSpec#formatCookieHeader() method produces a 'Set-Cookie' (request) header,
whereas CookieSpec#parse() method is intended to parse 'Cookie' (response)
Hi,
I am trying to run the following code for
www.google.com:
Cookie cookie = initialState.getCookies()[0];
CookieSpec cs = CookiePolicy.getDefaultSpec();
Header h = cs.formatCookieHeader(cookie);
Cookie[] cookie2 = cs.parse(cookie.getDomain(), 80,
cookie.getPath(), cookie.getSecure(), h);
And
nformation? Since it's not the secure
flag, my next two guesses would be:
1. mismatching host/domain names
2. mismatching path
As Mike suggested, a wire log would provide us with the
exact definition of the cookie and of the URLs. If you have
to obfuscate the URLs, please keep structural inf
On Apr 21, 2004, at 12:56 PM, Jean, Victor [IT] wrote:
Hi Mike,
Thanks for your response. I printed out the list of cookies set in
HttpState and found that all the cookie's secure flags are set to
false. I also tried adding the same cookie name/value/domain/path
with the false secure
Hi Mike,
Thanks for your response. I printed out the list of cookies set in HttpState and
found that all the cookie's secure flags are set to false. I also tried adding the
same cookie name/value/domain/path with the false secure flag without any success.
The http call does not seem t
Hi Victor,
My guess is that the "secure" flag is being set on this cookie. This
flag means that the cookie should only be sent over secure(HTTPS)
connections. You can get around this problem by manually adding a new
cookie (HttpState.addCookie()) with the same values, but setting
Hello,
I'm having an issue where a cookie set by posting to a https:// link is not being
recognized/picked up when i make a http:// call.
I'm using HttpClient and PostMethod to send username/password to be authenticated at
the https link. Once authenticated, a cookie is set by
--- Begin Message ---
Kazuya,
Per default HttpClient uses very strict RFC2109 compliant cookie spec, which requires
all cookies to have a version attribute. Those cookies that do not have an explicit
version attribute are assumed to be of version 0 (formatted according to the Netscape
cookie
em
occurred at application side. It is ASP application and it tires to use CInt function
to convert received cookie to integer but error occurred because "$version=0" was
included in it.
Thanks again
Kazuya Imabayashi
-Original Message-
From: Roland Weber [mailto:[EMAIL PROTECTED
Hello,
I can't tell for what reasons IE behaves as it does.
Cookies with version 0 are always formatted using
CookiePolicy.NETSCAPE. You can search for the
cookie in the HttpState, then use setVersion() to
change the version number. Then, the cookie will
be formatted by the default CookieP
: Re: cookie version info
Hello,
there are two versions of the Cookie spec, the old one (RFC 2109) and the new one (RFC
2965). Cookies that adhere to the new spec include version info when sent back to the
server. RFC 2965 also includes information about compatibility with older servers.
http
Hello,
there are two versions of the Cookie spec, the old one
(RFC 2109) and the new one (RFC 2965). Cookies that
adhere to the new spec include version info when sent
back to the server. RFC 2965 also includes information
about compatibility with older servers.
http://www.ietf.org/rfc/rfc2965
Hi there,
I have a small question regarding cookie handling.
When I execute GetMethod to some host, cookies are returned.
However, each cookie has its version info, like "$version=0".
An application of the target host cannot process this properly.
When I took some http traces via IE,
You're absolutely right, Roland, i was about sure about it but with your
confirmation, there is no doubt.
Thank you for your reply
-Original Message-
From: Roland Weber [mailto:[EMAIL PROTECTED]
Sent: mardi 24 fevrier 2004 13:05
To: Commons HttpClient Project
Subject: Re: Cookie rej
Hello Xavier,
your first action should be to contact the administrator of
that web site and tell him that the cookie configuration is
all screwed up.
No browser should accept a cookie for .smals-mvm.be
coming from socialsecurity.be, let alone HttpClient. It
would be a security violation to do so
ATTENTION: Cookie rejected:
"JSESSIONID=A7vh20mc7kV8j1gNcy0utYApOrPTzn2ZLLbX2zeY633eHw1xw5If!1167850
366!freyr.smals-mvm.be!8090!-1". Illegal domain attribute
".smals-mvm.be". Domain of origin: "socialsecurity.be"
I know this is a security/policy cookie problem and i
Kalnichevski, Oleg
I modified the HttpClient 2.0-RC3 code of
HeaderElement code to stop prasing by token by ",".
then i am able to get the cookie as of requirement.
Thanks
Hareesh.
--- "Kalnichevski, Oleg"
<[EMAIL PROTECTED]> wrote: > By
definition ent
HttpClient Project
Subject: RE: Cookie Problem
Kalnichevski, Oleg,
For this reason, i download the lastest build from cvs
of 20040215.zip.
Then i am getting this expection. But this code some
sort with httpclinet 2.0 rc3 version.
java.lang.IllegalArgumentException: Entity enclosing
requests cannot
e: > Hi
Hareesh,
>
> None of the cookie specs in the stable (HttpClient
> 2.0) branch can handle malformed cookies with
> unescaped commas. The development branch (HttpClient
> 3.0-pre-alpha) contains an improved Netscape cookie
> spec capable of handling commas in cookie val
Hi Hareesh,
None of the cookie specs in the stable (HttpClient 2.0) branch can handle malformed
cookies with unescaped commas. The development branch (HttpClient 3.0-pre-alpha)
contains an improved Netscape cookie spec capable of handling commas in cookie values.
For more details on the
Hi Roland Weber,
Thanks for you immediate reponse. Even if set the
cookie policy by different i am getting the problem.
Let me explain the problem i am facing, I am sending a
get request the home page of the xxx website, it is
comming fine, after that i am sending a post with user
and
Hello Hareesh,
the cookie shouldn't include commas in the first place,
that's a violation of the respective specification. But
since you have to access that page, try setting a
different cookie policy. Check out the options in
org.apache.commons.httpclient.cookie.CookiePolicy
Try NE
Hi,
I am working on website using apache commons
library of http client.
I was able to login into the website using my
code and not able navigate into website.
I was facing one problem with apache http client at
cookie assumption.
website is sending cookie like this way
Emre Sokullu wrote:
Hi all,
I have 3 questions :
1) How can I reject all cookies ? (code please)
public class NoCookieState extends HttpState {
public void addCookie(Cookie cookie) {
}
public void addCookies(Cookie[] cookies) {
}
}
HttpClient client = new HttpClient
On Sat, 2004-02-14 at 01:27, Emre Sokullu wrote:
> Thanx again Oleg...
>
> I didn't understand why redirection won't be allowed when old host and new
> host are the same.
>
> Forexample for one of my domains I made such a DNS arrangement :
>
> www.mydomain.com --> A --> M.Y.I.P
> mydomain.co
Thanx again Oleg...
I didn't understand why redirection won't be allowed when old host and new
host are the same.
Forexample for one of my domains I made such a DNS arrangement :
www.mydomain.com --> A --> M.Y.I.P
mydomain.com --> REDIRECT --> www.mydomain.com
So when trying to connec
On Fri, 2004-02-13 at 22:19, Emre Sokullu wrote:
> Hi Oleg,
>
> I have visited the link that you have given to me for the
> "setFollowRedirects()" problem:
> > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21216
>
> At this link, I've read that httpclient follows redirections for 100 times
>
Hi Oleg,
I have visited the link that you have given to me for the
"setFollowRedirects()" problem:
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21216
At this link, I've read that httpclient follows redirections for 100 times
by default.
So I've thought that if I knew the instance that d
On Fri, 2004-02-13 at 21:27, Emre Sokullu wrote:
> Thanx very much Oleg for your answers, I have a few things to say :
>
> > > 1) How can I reject all cookies ? (code please)
> >
> > This feature is only available in the development version of HttpClient
> > (3.0, which is currently in pre-alpha d
Thanx very much Oleg for your answers, I have a few things to say :
> > 1) How can I reject all cookies ? (code please)
>
> This feature is only available in the development version of HttpClient
> (3.0, which is currently in pre-alpha development stage). There's no
> straight-forward way to autom
Hi Emre
On Fri, 2004-02-13 at 20:21, Emre Sokullu wrote:
> Hi all,
>
> I have 3 questions :
>
> 1) How can I reject all cookies ? (code please)
This feature is only available in the development version of HttpClient
(3.0, which is currently in pre-alpha development stage). There's no
straight-
Hi all,
I have 3 questions :
1) How can I reject all cookies ? (code please)
2) How can I limit number of redirections for "setFollowRedirects()" method ? (code
please)
3) How can I skip entering proxy realm ? I mean :
Forexample for simple authentication, to skip the realm, we use
"setAuth
David,
Use browser compatibility cookie policy instead of stricter RFC 2109. For more details
see <http://jakarta.apache.org/commons/httpclient/cookies.html>
Cheers,
Oleg
-Original Message-
From: David Webb [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 22, 2004 16:10
To:
I am getting the following error from HttpClient and I would like to know if
nayone can suggest a solution.
violates RFC 2109: host minus domain may not contain any dots
The machine name is machine.fl.mydomain.com and the domain attribute
is .mydomain.com. Can I tell HttpClient to ignore this
gzilla/show_bug.cgi?id=25264
Cookie rejected
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Reso
(CookiePolicy.COMPATIBILITY);
Cookie[] cookies = request.getCookies();//This method call gives all the cookies in
response to the browser request..
}
Thanks
Venkat Burri
-Original Message-
From: Michael Becke [mailto:[EMAIL PROTECTED]
Sent: Fri 1/2/2004 8:56 AM
To
Hi Jacques,
HttpClient automatically processes cookie in the response and adds any
new cookies to the associated HttpState. Take a look at
HttpClient.getState() and HttpState.getCookies(). There is also some
more info on cookie parsing at
<http://jakarta.apache.org/commons/httpcli
Hi there (pls ignore my previous post)
I'm using HttpClient to write a Cactus unit test. I'd
like to simulate a browser, sending a cookie to the
server with a request. So the cookie originates at the
client side :
HttpClient client = new HttpClient();
HttpMethod method = new get
Hi there
I'm using HttpClient to write a Cactus unit test. I'd
like to simulate a browser, sending a cookie to the
server with a request. So the cookie originates at the
client side :
HttpClient client = new HttpClient();
HttpMethod method = new getMethod(url);
String cookieValue =
gzilla/show_bug.cgi?id=25264
Cookie rejected
--- Additional Comments From [EMAIL PROTECTED] 2003-12-16 19:06 ---
Created an attachment (id=9599)
Patch against 2.0 (take 1)
-
To unsubscribe, e-mail: [EMAIL PROTECTE
gzilla/show_bug.cgi?id=25264
Cookie rejected
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
Target Mil
gzilla/show_bug.cgi?id=25264
Cookie rejected
--- Additional Comments From [EMAIL PROTECTED] 2003-12-15 18:18 ---
The code is here, have a look to the login() method in FileReleaseSystemBean.
The trick is to hit Sourceforge first with a GET method, then send the POST
method with the
gzilla/show_bug.cgi?id=25264
Cookie rejected
--- Additional Comments From [EMAIL PROTECTED] 2003-12-15 17:52 ---
Ludovic,
Would it be possible for you to post the code you are using to connect to
sourceforge.net? I am trying to reproduce the problem but cannot even get the
site to send tha
gzilla/show_bug.cgi?id=25264
Cookie rejected
--- Additional Comments From [EMAIL PROTECTED] 2003-12-09 13:22 ---
Oleg,
You are quite right. I missed the code in RFC2109. I look forward to seeing what
happens with SF.
[EMAIL PROTECTED] wrote:
Roland,
I still must have a dormant Sourceforce account. I'll take a closer look at the
Sourceforce login procedure and provide a patch for our browser compatibility
cookie spec if required
Oleg
I also have a SF.net account. If someone would post some code I ca
gzilla/show_bug.cgi?id=25264
Cookie rejected
--- Additional Comments From [EMAIL PROTECTED] 2003-12-09 09:13 ---
> I've also noticed that the current domain match implementation matches
> "y.x.foo.com" with ".foo.com", though this is explicitly disallowed in
[EMAIL PROTECTED] wrote:
Browser makers have
gotten a lot of public beating for security bugs lately, and I'd
consider this to be one.
Yep, I guess Safari currently exposes all it's cookies to anyone who
wants to read them :-)
---
gzilla/show_bug.cgi?id=25264
Cookie rejected
--- Additional Comments From [EMAIL PROTECTED] 2003-12-09 07:17 ---
Please ignore my last comment about the cookie parsing. I mixed up
the cookie domain and the host. The cookie is parsed correctly, the
problem lies with the hostname.
However
gzilla/show_bug.cgi?id=25264
Cookie rejected
--- Additional Comments From [EMAIL PROTECTED] 2003-12-09 07:00 ---
Hello Mike,
are you sure about the domain-matching thing? Here's a snippet from
RFC 2965, section 1, page 1:
> Note that domain-match is not a commutative operat
gzilla/show_bug.cgi?id=25264
Cookie rejected
--- Additional Comments From [EMAIL PROTECTED] 2003-12-09 05:18 ---
Oleg,
I think we should make an attempt to be as forgiving as possible when in compatibility
mode, with
the exception of places where there are security considerations. I&#
gzilla/show_bug.cgi?id=25264
Cookie rejected
--- Additional Comments From [EMAIL PROTECTED] 2003-12-08 21:22 ---
Folks,
I think we all agree that the cookie is broken, and the problem lies with
sourceforge, but the real trouble is that browsers (as well as so called
browsers developed by THA
gzilla/show_bug.cgi?id=25264
Cookie rejected
--- Additional Comments From [EMAIL PROTECTED] 2003-12-08 13:31 ---
Hi Ludovic,
I agree with Roland. The problem really lies with sourceforge, and most likely there
is another
login URL with an appropriate domain.
As for custom cookie po
gzilla/show_bug.cgi?id=25264
Cookie rejected
--- Additional Comments From [EMAIL PROTECTED] 2003-12-08 07:09 ---
Hello Ludovic,
HttpClient works correctly in this case. RFC 2965 defines in section 1
the comparison operations on hosts and domain names. The *host*
sourceforge.net is not matc
gzilla/show_bug.cgi?id=25264
Cookie rejected
--- Additional Comments From [EMAIL PROTECTED] 2003-12-07 19:02 ---
Oleg,
I understand your reluctance to apply the patch, it can create more issues than
good.
I've tried to use the HEAD release, and the cookie plugin mecanism works wel
gzilla/show_bug.cgi?id=25264
Cookie rejected
--- Additional Comments From [EMAIL PROTECTED] 2003-12-07 00:52 ---
Ludovic,
In my opinion the cookie is clearly wrong. Somehow I do not feel like patching
HttpClient because of evey single broken cookie out there.
Besides, your patch seems to f
gzilla/show_bug.cgi?id=25264
Cookie rejected
--- Additional Comments From [EMAIL PROTECTED] 2003-12-07 00:24 ---
This patch solves the problem when using CookieSpecBase (COMPATIBILITY)
diff -r1.20 CookieSpecBase.java
424a425
> String cookieDomain = cookie.getDomain();
43
gzilla/show_bug.cgi?id=25264
Cookie rejected
Summary: Cookie rejected
Product: Commons
Version: 1.0 Beta 2
Platform: PC
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Http
Hello Eric,
>From RFC 2965, HTTP State Management, Section 3:
value = token | quoted-string
[...]
cookie = NAME "=" VALUE *(";" set-cookie-av)
VALUE = value
That is part of the BNF grammar for the set-cookie2 header.
All
o webapps, then started
> >>up Tomcat with a "./catalina.sh run". Then I ran the tests as reported.
> >>
> >>-Eric.
> >>
> >>Kalnichevski, Oleg wrote:
> >>
> >>
> >>
> >>>Eric,
> >>>Stran
and had no failing test cases of whatsoever. I reran the test cases with the latest code from CVS HEAD and 2.0 branch against Tomcat 4.1.29 after having read your message. Again, no failing test cases.
Did you keep your old server.xml file?
Oleg
-Original Message-
From: Eric Johnson [mailto
ving read your message. Again, no failing test
> >cases.
> >
> >Did you keep your old server.xml file?
> >
> >Oleg
> >
> >-Original Message-
> >From: Eric Johnson [mailto:[EMAIL PROTECTED]
> >Sent: Tuesday, November 04, 2003 17:11
> >To: HttpClie
e latest code from CVS HEAD and 2.0 branch against Tomcat 4.1.29 after having read your message. Again, no failing test cases.
Did you keep your old server.xml file?
Oleg
-Original Message-
From: Eric Johnson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 04, 2003 17:11
To: HttpClient
file?
Oleg
-Original Message-
From: Eric Johnson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 04, 2003 17:11
To: HttpClient
Subject: Cookie test case failures with Tomcat 4.1.29
It would seem that the latest Tomcat (4.1.29) has engaged in a subtle
change in behavior with respect
It would seem that the latest Tomcat (4.1.29) has engaged in a subtle
change in behavior with respect to cookies. When I ran it this morning,
nine of the cookie related test cases failed. Last week, I was running
with Tomcat 4.1.27, and everything worked fine.
Since I had it readily
gzilla/show_bug.cgi?id=24332
Cookie docs are outdated.
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
gzilla/show_bug.cgi?id=24332
Cookie docs are outdated.
--- Additional Comments From [EMAIL PROTECTED] 2003-11-04 02:39 ---
Patch applied. Link fixed.
Mike
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comma
gzilla/show_bug.cgi?id=24332
Cookie docs are outdated.
--- Additional Comments From [EMAIL PROTECTED] 2003-11-03 18:37 ---
Mike, looks good. Go ahead, commit it. Oleg
PS:
Currently the 'Sample code' URL on the HttpClient's site points to CVS HEAD
which can easily cause co
gzilla/show_bug.cgi?id=24332
Cookie docs are outdated.
--- Additional Comments From [EMAIL PROTECTED] 2003-11-03 12:15 ---
Ooops Sorry, the attachment entitled "Result of changing the
HttpMethodBase#2449" was for other bug!!. Can please someone delete
gzilla/show_bug.cgi?id=24332
Cookie docs are outdated.
--- Additional Comments From [EMAIL PROTECTED] 2003-11-03 12:11 ---
Created an attachment (id=8885)
Result of changing the HttpMethodBase#2449
-
To unsubscribe,
gzilla/show_bug.cgi?id=24081
Manually set 'Cookie' & 'Authorization' headers get discarded
--- Additional Comments From [EMAIL PROTECTED] 2003-11-03 04:25 ---
Funny,
When I reported this bug, I was told this would never get fixed.
gzilla/show_bug.cgi?id=24332
Cookie docs are outdated.
--- Additional Comments From [EMAIL PROTECTED] 2003-11-02 19:11 ---
Please take a look and let me know. I will commit this tomorrow if there are no
objections or
additions.
gzilla/show_bug.cgi?id=24332
Cookie docs are outdated.
--- Additional Comments From [EMAIL PROTECTED] 2003-11-02 19:11 ---
Created an attachment (id=8873)
Patch 1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addi
gzilla/show_bug.cgi?id=24332
Cookie docs are outdated.
Summary: Cookie docs are outdated.
Product: Commons
Version: Nightly Builds
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Com
gzilla/show_bug.cgi?id=24081
Manually set 'Cookie' & 'Authorization' headers get discarded
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNE
gzilla/show_bug.cgi?id=24081
Manually set 'Cookie' & 'Authorization' headers get discarded
--- Additional Comments From [EMAIL PROTECTED] 2003-11-01 23:34 ---
Looks good to me.
Mike
-
To unsubsc
gzilla/show_bug.cgi?id=24081
Manually set 'Cookie' & 'Authorization' headers get discarded
--- Additional Comments From [EMAIL PROTECTED] 2003-10-30 08:35 ---
Hello Oleg,
I have just taken a look at it. In combination with pluggable cookie policies,
this patch pr
gzilla/show_bug.cgi?id=24081
Manually set 'Cookie' & 'Authorization' headers get discarded
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW
gzilla/show_bug.cgi?id=24081
Manually set 'Cookie' & 'Authorization' headers get discarded
--- Additional Comments From [EMAIL PROTECTED] 2003-10-23 21:52 ---
Created an attachment (id=8711)
Patch (take 1)
-
1 - 100 of 234 matches
Mail list logo
