hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rezaei, Mohammad A." <mohammad.rez...@gs.com>
Subject RE: [RFE] provide request entities in a more abstract way
Date Thu, 26 Feb 2004 15:57:04 GMT
I see. If we limit the retries to 401 and 407, we're safe, per the RFC:
401:
"The client MAY repeat the
   request with a suitable Authorization header field"
407:
"The
   client MAY repeat the request with a suitable Proxy-Authorization
   header field "

Most of the other 40x are fatal and should not be retried.
So a simple interface (3 methods: isRetriable(), resetStream(),
getInputStream() ??) sounds like a good idea.

Thanks
Moh

>-----Original Message-----
>From: Roland Weber [mailto:ROLWEBER@de.ibm.com] 
>Sent: Thursday, February 26, 2004 10:13 AM
>To: Commons HttpClient Project
>Subject: RE: [RFE] provide request entities in a more abstract way
>
>
>Hello Moh,
>
>you are assuming preemptive authentication.
>In general, authentication is triggered by a 40x
>response from the server, which means the
>request has already been sent.
>
>best regards,
>  Roland
>
>
>
>
>
>"Rezaei, Mohammad A." <mohammad.rezaei@gs.com>
>26.02.2004 15:57
>Please respond to "Commons HttpClient Project"
> 
>        To:     "'Commons HttpClient Project'" 
><commons-httpclient-dev@jakarta.apache.org>
>        cc: 
>        Subject:        RE: [RFE] provide request entities in a more 
>abstract way
>
>
>Both authentication and closed connections should occur long before we 
>read
>the input stream to send the request body. So why would you 
>want to reset the stream?
>
>Thanks
>Moh
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org


Mime
View raw message