http fluent多种请求

╰半夏微凉° 2022-05-20 07:43 152阅读 0赞

来自：https://blog.csdn.net/chenpeng19910926/article/details/71719205

1.  String( "Important stuff", ContentType.DEFAULT\_TEXT)
2.  .execute().returnContent().asBytes();

1.  *// Execute a POST with a custom header through the proxy containing a request body*
2.  *// as an HTML form and save the result to the file*
3.  Request.Post( "http://somehost/some-form")
4.  .addHeader( "X-Custom-header", "stuff")
5.  .viaProxy( new HttpHost( "myproxy", 8080))
6.  .bodyForm(Form.form().add( "username", "vip").add( "password", "secret").build())
7.  .execute().saveContent( new File( "result.dump"));

*还可以直接使用Executor，以便在特定的安全上下文中执行请求，从而将身份验证细节缓存并重新用于后续请求。*

1.  Executor executor = Executor.newInstance()
2.  .auth( new HttpHost( "somehost"), "username", "password")
3.  .auth( new HttpHost( "myproxy", 8080), "username", "password")
4.  .authPreemptive( new HttpHost( "myproxy", 8080));
5.  
6.  executor.execute(Request.Get( "http://somehost/"))
7.  .returnContent().asString();
8.  
9.  executor.execute(Request.Post( "http://somehost/do-stuff")
10. .useExpectContinue()
11. .bodyString( "Important stuff", ContentType.DEFAULT\_TEXT))
12. .returnContent().asString();

### 5.1.1. Response 处理    ###

fluent facade *API通常减轻用户不必处理连接管理和资源释放。**然而，在大多数情况下，这是以缓冲内存中的响应消息内容为代价的。 强烈建议使用ResponseHandler进行HTTP响应处理，以避免在内存中缓冲的内容丢失。*

1.  Document result = Request.Get( "http://somehost/content")
2.  .execute().handleResponse( new ResponseHandler<Document>() \{
3.  
4.  public Document handleResponse(final HttpResponse response) throws IOException \{
5.  StatusLine statusLine = response.getStatusLine();
6.  HttpEntity entity = response.getEntity();
7.  if (statusLine.getStatusCode() >= 300) \{
8.  throw new HttpResponseException(
9.  statusLine.getStatusCode(),
10. statusLine.getReasonPhrase());
11. \}
12. if (entity == null) \{
13. throw new ClientProtocolException( "Response contains no content");
14. \}
15. DocumentBuilderFactory dbfac = DocumentBuilderFactory.newInstance();
16. try \{
17. DocumentBuilder docBuilder = dbfac.newDocumentBuilder();
18. ContentType contentType = ContentType.getOrDefault(entity);
19. if (!contentType.equals(ContentType.APPLICATION\_XML)) \{
20. throw new ClientProtocolException( "Unexpected content type:" \+
21. contentType);
22. \}
23. String charset = contentType.getCharset().displayName();
24. if (charset == null) \{
25. charset = "UTF-8";
26. \}
27. return docBuilder.parse(entity.getContent(), charset);
28. \} catch (ParserConfigurationException ex) \{
29. throw new IllegalStateException(ex);
30. \} catch (SAXException ex) \{
31. throw new ClientProtocolException( "Malformed XML document", ex);
32. \}
33. \}
34. 
35. \});

总结：我个人感觉这个功能非常的棒，如果对于HTTP请求报文设置相对较少或者需求较为简单这种方法处理很方便，减少了很多臃肿的代码。