DO NOT REPLY [Bug 15435] - New Preferences Architecture

2003-09-17 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: HTTP/1.1 status 100 help needed

2003-09-17 Thread Oleg Kalnichevski
Oh. well, I knew it. This is a very strange quirk on the part of Jetty, which once was reported as a bug, but Jetty folks were not too enthusiastic to fix. Anyways, try this: PostMethod#setUseExpectHeader(true) and see if that makes any difference. If not, try disabling HTTP/1.1 support altoget

RE: HTTP/1.1 status 100 help needed

2003-09-17 Thread Beg, Mohsin
Hi Oleg, Below is my server info. Also can you point me to some code examples as how I may be able to do what you suggested ? Sincerely, -Mohsin 2003/09/17 13:54:59:809 PDT [DEBUG] wire - -<< "Date: Wed, 17 Sep 2003 20:54:59 GMT[\r][\n]" 2003/09/17 13:54:59:813 PDT [DEBUG] wire - -<< "Server

DO NOT REPLY [Bug 15435] - New Preferences Architecture

2003-09-17 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: [PATCH] Reworked digest auth

2003-09-17 Thread Oleg Kalnichevski
Odi, the patch looks fine to me. I just dislike this part: try { cnonce = createCnonce(); } catch(AuthenticationException e) { throw new RuntimeException(e.toString()); } At the very least I would rethrow the exception as MalformedChallengeEx

Re: HTTP/1.1 status 100 help needed

2003-09-17 Thread Oleg Kalnichevski
Mohsin, Do you know what kind of HTTP server runs on the server side? The HTTP server appears to be using the 'expect: 100-continue' handshake even though the client did not request it. You may what to try the following measures: - activating 'expect: 100-continue' on the client side - using HTT

HTTP/1.1 status 100 help needed

2003-09-17 Thread Beg, Mohsin
Hello, I have the following code snippet that seems to never return from httpClient.executeMethod(). [actually another post has happened that issued a cookie that the code below is trying to use] I have also attached a modified/truncated output of the logs that are are being produced. Can someo

RE: Seeking help using Cookie and Session

2003-09-17 Thread Kalnichevski, Oleg
Eric, I think we should keep 'recycle' for another while. Once we have HttpMethod split into HttpRequest/HttpResponse pair of interfaces, a request object may be reused as many times are needed without having to resort to recycling tricks of any sort. Oleg -Original Message- From: Eri

Re: Seeking help using Cookie and Session

2003-09-17 Thread Dan Tran
Dear Eric and Oleg, I put in the code to handle brower compatibility cookie. Now it works. Thank you Thank you. Eric, thanks for the advice. I took out recycle call and handle releaseConnection correctly. Thanks for every thing -Dan - Original Message - From: "Eric Johnson" <[EMAIL PR

Re: Seeking help using Cookie and Session

2003-09-17 Thread Eric Johnson
A follow-up question, directed towards the rest of the group Shouldn't "recycle" be deprecated for the 2.1 release? Seems like we've discussed it before, and all it gives us is a chance for uses like the following, where my first reaction was that maybe the "recycle" call didn't work prope

RE: Seeking help using Cookie and Session

2003-09-17 Thread Kalnichevski, Oleg
Dan, Before I could give you a more precise answer, I would need some additional input from you. - What kind of cookie policy have you been using? Have you tried using browser compatibility policy? If unsure, you may want to consult our cookie guide:

Seeking help using Cookie and Session

2003-09-17 Thread Dan Tran
Hi I am write a small client/server web app to understand more about httpclient/cookie/and httpsession. On the httpclient side, I use a get method to keep calling a servlet on server. HttpClient client = new HttpClient(); GetMethod method = new GetMethod(url); while ( !done ) {

Re: [PATCH] Reworked digest auth

2003-09-17 Thread Ortwin Glück
Take 2: - DigestScheme requires a nonce in every challange now (according to RFC 2617) test cases changed accordingly - included Olegs feedback After reading RFC 2617 I came to the conclusion, that we need to rework out authentication mechanism to support stateful authentication retries. Diges