はてなブックマーク

Index of /httpcomponents-client-ga/fluent-hc NameLast modifiedSizeDescription Parent Directory  - apidocs/2020-03-07 09:44 - checkstyle.html2020-03-07 09:44 3.8K checkstyle.rss2020-01-22 16:19 4.4K clirr-report.html2020-03-07 09:44 5.0K css/2020-07-23 16:11 - dependencies.html2020-03-07 09:44 23K dependency-info.html2020-03-07 09:44 4.4K examples/2018-05-01 20:49 - images/2018-05-01 20:49 - projec

Originally HTTP was designed as a stateless, request / response oriented protocol that made no special provisions for stateful sessions spanning across several logically related request / response exchanges. As HTTP protocol grew in popularity and adoption more and more systems began to use it for applications it was never intended for, for instance as a transport for e-commerce applications. Thus

Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at ht

Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at ht

The process of establishing a connection from one host to another is quite complex and involves multiple packet exchanges between two endpoints, which can be quite time consuming. The overhead of connection handshaking can be significant, especially for small HTTP messages. One can achieve a much higher data throughput if open connections can be re-used to execute multiple requests. HTTP/1.1 state

Exception handling There are two main type of exceptions that the user of HttpClient may encounter when executing HTTP methods: transport exceptions protocol exceptions Not all of these exceptions will be propagated to the user in regular HttpClient use. Exceptions handled internally by HttpClient are marked below as INTERNAL. Transport exceptions Protocol exceptions HTTP transport safety Automati

Overview This tutorial is designed to provide a basic overview of how to use HttpClient. When you have completed the tutorial you will have written a simple application that downloads a page using HttpClient. It is assumed that you have an understanding of how to program in Java and are familiar with the development environment you are using. Getting Ready The first thing you need to do is get a c

Quality and extent of the HTTP/1.0 and HTTP/1.1 spec compliance vary significantly among commonly used HTTP agents and HTTP servers. That requires of HttpClient to be able to mimic (mis-)behavior of widely used web browsers; support flexible and configurable level of leniency toward non-critical protocol violations especially in those gray areas of the specification subject to different, at times

Introduction HttpClient provides full support for HTTP over Secure Sockets Layer (SSL) or IETF Transport Layer Security (TLS) protocols by leveraging the Java Secure Socket Extension (JSSE). JSSE has been integrated into the Java 2 platform as of version 1.4 and works with HttpClient out of the box. On older Java 2 versions JSSE needs to be manually installed and configured. Installation instructi

Introduction This document provides an overview of how to use HttpClient safely from within a multi-threaded environment. It is broken down into the following main sections: MultiThreadedHttpConnectionManager Connection Release Please see the MultiThreadedExample for a concrete example. MultiThreadedHttpConnectionManager The main reason for using multiple theads in HttpClient is to allow the execu

You must define the maven.xdoc.distributionUrlproperty if you wish to generate the download report.

End of life The Commons HttpClient project is now end of life, and is no longer being developed. It has been replaced by the Apache HttpComponents project in its HttpClient and HttpCore modules, which offer better performance and more flexibility. Introduction The Hyper-Text Transfer Protocol (HTTP) is perhaps the most significant protocol used on the Internet today. Web services, network-enabled

<H2> Frame Alert</H2> <P> This document is designed to be viewed using the frames feature. If you see this message, you are using a non-frame-capable web client. <BR> Link to<A HREF="overview-summary.html">Non-frame version.</A>