Ah! That answers that :) I'll probably create a branch for 4.1 integration and OAuth support but I probably won't want to depend on it until it at least reaches beta stage. But thank you for the response. I'll look forward to it :)
-Tom On Thu, Sep 9, 2010 at 5:25 PM, Oleg Kalnichevski <ol...@apache.org> wrote: > On Thu, 2010-09-09 at 17:20 -0400, Thom Nichols wrote: > > I understand how the HTTP request is represented on the wire, but > > HttpRequest.getURI() will still hold the full URI (except I'm guessing in > > the situation of redirects and auths where > 1 request is made.) The > > original request.getURI() returned the full URI: > > http://twitter.com/statuses/update.xml > > > > Looking at the headers, I can get the Host, but not scheme: > > Accept : application/xml, text/xml, application/xhtml+xml > > Content-Length : 91 > > Content-Type : application/x-www-form-urlencoded; charset=MacRoman > > *Host : twitter.com:80* > > Connection : Keep-Alive > > Cookie :.... > > Cookie2 : .... > > > > So I can _mostly_ reconstruct the request URI. But I don't think I can > > reliably get the scheme. > > > > > > > Tom, > > The fact that HttpContext is not passed to the AuthScheme is one of the > biggest API blunders in 4.0. If you can upgrade to 4.1-alpha, make your > custom auth scheme implement ContextAwareAuthScheme instead > > > http://hc.apache.org/httpcomponents-client/httpclient/apidocs/org/apache/http/auth/ContextAwareAuthScheme.html > > Oleg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org > For additional commands, e-mail: dev-h...@hc.apache.org > >
