[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538390#comment-13538390
 ] 

Oleg Kalnichevski commented on HTTPCLIENT-900:
----------------------------------------------

Noah,
Yes, 4.3 API is still being developed and is unstable. However, id you start 
using it early you can still influence the way it evolves.

The trouble with BasicHttpRequest is that it is provided by the core module 
whereas the HttpExecutionAware interface is client specific.

Oleg
                
> Don't enforce URI syntax
> ------------------------
>
>                 Key: HTTPCLIENT-900
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-900
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: HttpClient
>    Affects Versions: 4.0 Final
>            Reporter: Marko Asplund
>            Priority: Minor
>             Fix For: 4.3 Alpha1
>
>
> I'm trying to use HttpComponents Client for fetching data from a web site.
> I've ran into problems that seem to be related with the way the request URL 
> query parameters are handled on the server side.
> The service doesn't encode unsafe characters (e.g. '{' and '}') in response 
> URLs.
> Also when these characters are encoded on the client prior to issuing the 
> request the service gives incorrect responses.
> The URLs are of the following form:
> http://www.foo.bar/foobar?${APPL}=hetekaue
> On the otherhand HC Client doesn't allow me to send requests with invalid 
> query syntax
> (HttpGet(String) constructor throws an URISyntaxException).
> It would be good if HC Client could be used also in situations like this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to