am also interested in this topics, as i also have problems on handling requests ( e.g some requests are encoded with latin, others with utf-8, so parsing it will sometimes fail )
concerning extendings HttpRequestWriter: is it true that you'll have to extract the path out of the uri anyway ? (example: u'll mostly write "GET /resource/file?param1=value1 HTTP/1.1" instead of "GET http://example.com:8080/resource/file?param1=value1 HTTP/1.1" so you'll still need to use URI to extract the path after the host-name and will get the same issue. thanx On Sat, Jan 14, 2012 at 6:40 PM, becks007 <[email protected]> wrote: > > Thanks a lot Oleg. > > HttpRequestWriter seems perfect. > > I will try out a custom/extended implementation for HttpRequestWriter by > overriding > org.apache.http.impl.AbstractHttpClientConnection.createRequestWriter() > under a extended implementation for > org.apache.http.impl.DefaultHttpClientConnection(). > Then extend HttpPut/HttpGet add a separate method to return un-encoded URL > as string then use that value in extended > org.apache.http.impl.io.HttpRequestWriter. > > regards > becks > -- > View this message in context: > http://old.nabble.com/workaround-for-RFC-3986-based-java.net.URI-url-failures-tp33123835p33140148.html > Sent from the HttpClient-User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
