HttpClient - When to use HttpHost parameter when executing HttpRequest
When using the following code:
URIBuilder uriBuilder = new URIBuilder(url);
HttpPost httpRequest= new HttpPost(uriBuilder.build());
HttpHost httpHost= new HttpHost(uriBuilder.getHost(), uriBuilder.getPort(), uriBuilder.getScheme());
When is it a good practice to use
httpClient.execute(httpHost, httpRequest);
Because httpHost's host can be determined by HttpRequest which includes the URL
/**
* Executes HTTP request using the default context.
*
* @param target the target host for the request.
* Implementations may accept {@code null}
* if they can still determine a route, for example
* to a default target or by inspecting the request.
* @param request the request to execute
*
* @return the response to the request. This is always a final response,
* never an intermediate response with an 1xx status code.
* Whether redirects or authentication challenges will be returned
* or handled automatically depends on the implementation and
* configuration of this client.
* @throws IOException in case of a problem or the connection was aborted
* @throws ClientProtocolException in case of an http protocol error
*/
HttpResponse execute(HttpHost target, HttpRequest request)
Is there any benefit over calling
httpClient.execute(httpRequest);
Is it proxy/firewall/balancer related solution? When host will be different than URL's host?
httprequest httpclient apache-commons-httpclient http-host
add a comment |
When using the following code:
URIBuilder uriBuilder = new URIBuilder(url);
HttpPost httpRequest= new HttpPost(uriBuilder.build());
HttpHost httpHost= new HttpHost(uriBuilder.getHost(), uriBuilder.getPort(), uriBuilder.getScheme());
When is it a good practice to use
httpClient.execute(httpHost, httpRequest);
Because httpHost's host can be determined by HttpRequest which includes the URL
/**
* Executes HTTP request using the default context.
*
* @param target the target host for the request.
* Implementations may accept {@code null}
* if they can still determine a route, for example
* to a default target or by inspecting the request.
* @param request the request to execute
*
* @return the response to the request. This is always a final response,
* never an intermediate response with an 1xx status code.
* Whether redirects or authentication challenges will be returned
* or handled automatically depends on the implementation and
* configuration of this client.
* @throws IOException in case of a problem or the connection was aborted
* @throws ClientProtocolException in case of an http protocol error
*/
HttpResponse execute(HttpHost target, HttpRequest request)
Is there any benefit over calling
httpClient.execute(httpRequest);
Is it proxy/firewall/balancer related solution? When host will be different than URL's host?
httprequest httpclient apache-commons-httpclient http-host
add a comment |
When using the following code:
URIBuilder uriBuilder = new URIBuilder(url);
HttpPost httpRequest= new HttpPost(uriBuilder.build());
HttpHost httpHost= new HttpHost(uriBuilder.getHost(), uriBuilder.getPort(), uriBuilder.getScheme());
When is it a good practice to use
httpClient.execute(httpHost, httpRequest);
Because httpHost's host can be determined by HttpRequest which includes the URL
/**
* Executes HTTP request using the default context.
*
* @param target the target host for the request.
* Implementations may accept {@code null}
* if they can still determine a route, for example
* to a default target or by inspecting the request.
* @param request the request to execute
*
* @return the response to the request. This is always a final response,
* never an intermediate response with an 1xx status code.
* Whether redirects or authentication challenges will be returned
* or handled automatically depends on the implementation and
* configuration of this client.
* @throws IOException in case of a problem or the connection was aborted
* @throws ClientProtocolException in case of an http protocol error
*/
HttpResponse execute(HttpHost target, HttpRequest request)
Is there any benefit over calling
httpClient.execute(httpRequest);
Is it proxy/firewall/balancer related solution? When host will be different than URL's host?
httprequest httpclient apache-commons-httpclient http-host
When using the following code:
URIBuilder uriBuilder = new URIBuilder(url);
HttpPost httpRequest= new HttpPost(uriBuilder.build());
HttpHost httpHost= new HttpHost(uriBuilder.getHost(), uriBuilder.getPort(), uriBuilder.getScheme());
When is it a good practice to use
httpClient.execute(httpHost, httpRequest);
Because httpHost's host can be determined by HttpRequest which includes the URL
/**
* Executes HTTP request using the default context.
*
* @param target the target host for the request.
* Implementations may accept {@code null}
* if they can still determine a route, for example
* to a default target or by inspecting the request.
* @param request the request to execute
*
* @return the response to the request. This is always a final response,
* never an intermediate response with an 1xx status code.
* Whether redirects or authentication challenges will be returned
* or handled automatically depends on the implementation and
* configuration of this client.
* @throws IOException in case of a problem or the connection was aborted
* @throws ClientProtocolException in case of an http protocol error
*/
HttpResponse execute(HttpHost target, HttpRequest request)
Is there any benefit over calling
httpClient.execute(httpRequest);
Is it proxy/firewall/balancer related solution? When host will be different than URL's host?
httprequest httpclient apache-commons-httpclient http-host
httprequest httpclient apache-commons-httpclient http-host
edited Jan 2 at 6:45
user7294900
asked Jan 2 at 5:19


user7294900user7294900
23.3k113363
23.3k113363
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
From the docs,
Implementations may accept null if they can still determine a route,
for example to a default target or by inspecting the request.
Your question
httpHost's host can be determined by HttpRequest which includes the
URL
just paraphrases what is written in the docs.
There is no benefit of calling one over the other in your case. But, for advanced configurations, you can refer this where explicitly you may need to use HTTPHost. Hope this helps!
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54001561%2fhttpclient-when-to-use-httphost-parameter-when-executing-httprequest%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
From the docs,
Implementations may accept null if they can still determine a route,
for example to a default target or by inspecting the request.
Your question
httpHost's host can be determined by HttpRequest which includes the
URL
just paraphrases what is written in the docs.
There is no benefit of calling one over the other in your case. But, for advanced configurations, you can refer this where explicitly you may need to use HTTPHost. Hope this helps!
add a comment |
From the docs,
Implementations may accept null if they can still determine a route,
for example to a default target or by inspecting the request.
Your question
httpHost's host can be determined by HttpRequest which includes the
URL
just paraphrases what is written in the docs.
There is no benefit of calling one over the other in your case. But, for advanced configurations, you can refer this where explicitly you may need to use HTTPHost. Hope this helps!
add a comment |
From the docs,
Implementations may accept null if they can still determine a route,
for example to a default target or by inspecting the request.
Your question
httpHost's host can be determined by HttpRequest which includes the
URL
just paraphrases what is written in the docs.
There is no benefit of calling one over the other in your case. But, for advanced configurations, you can refer this where explicitly you may need to use HTTPHost. Hope this helps!
From the docs,
Implementations may accept null if they can still determine a route,
for example to a default target or by inspecting the request.
Your question
httpHost's host can be determined by HttpRequest which includes the
URL
just paraphrases what is written in the docs.
There is no benefit of calling one over the other in your case. But, for advanced configurations, you can refer this where explicitly you may need to use HTTPHost. Hope this helps!
edited Jan 2 at 6:17
answered Jan 2 at 6:00


Mohamed Anees AMohamed Anees A
1,226420
1,226420
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54001561%2fhttpclient-when-to-use-httphost-parameter-when-executing-httprequest%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown