On Thu, 2007-10-25 at 14:18 +0200, [EMAIL PROTECTED] wrote: > Hello Odi, > > > No, we must not prepend a / as this would change the semantics. > > What is the semantics of something that is not specified? > RFC 2616 requires absolute URIs. (section 14.30) > > > Instead the resulting URI must be resolved against the request URI: > > Or the Content-Location header, if present? > I suggest to trigger an exception for relative paths. >
Roland We do, but only if the 'http.protocol.reject-relative-redirect' parameter is explicitly set to true. If my memory does not fail me, the parameter was introduced in the early days of HttpClient 3.0 when there was simply no way to override the default logic of redirect handling. Now that we have pluggable redirect handlers we can provide two implementations: a strict one and a lenient one and do away with the parameter. Alternatively we could set the parameter to true per default Oleg > cheers, > Roland > > --------------------------------------------------------------------- > 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]
