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 >-----Original Message----- >From: Ortwin Glück [mailto:[EMAIL PROTECTED] >Sent: Thursday, February 26, 2004 9:56 AM >To: Commons HttpClient Project >Subject: Re: [RFE] provide request entities in a more abstract way > > >Rezaei, Mohammad A. wrote: >> This is a bad idea. The HTTP RFC (2616) explicitly forbids auto >> retries: >> >> "Non-idempotent methods or sequences >> MUST NOT be automatically retried, although user agents >MAY offer a >> human operator the choice of retrying the request(s). " >> >> So if retries are not good, then what's the point of the interface? >> >> Thanks >> Moh > >Moh, > >please note that I refer "retry" as resending the request if it fails >due to > a) authentication > b) closed connection from the pool > >HttpClient already has this functionality, but it is just not possible >to use it with unbuffered request entities. > >O. > >--------------------------------------------------------------------- >To unsubscribe, e-mail: >[EMAIL PROTECTED] >For additional commands, e-mail: >[EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
