Commons

Home

Information

Project Files

About Us

Jakarta Community

Introduction

The scope of the HTTP Client component is an implementation of the HTTP protocol, as defined in RFC 2616 and related specifications.

The original source was donated by the Jakarta Slide project.


Dependencies

HTTP Client is dependent upon the following external components for run-time use:

Java Development Kit
(Version 1.2 or later. Note that the "external" interface of HTTP Client is JDK 1.1 compatible, hence a JDK 1.1 compatible distribution could be created.)

The following external components may be used with HTTP Client to support certain optional features:

Java Secure Socket Extension
(Version 1.0.2 or later)
Only needed if you're using HTTPS.
Log4J
HTTP Client supports but does not require Log4J logging.

The following tools are recommended for those who wish to develop the HTTP Client component:

Jakarta Ant
(Version 1.2 or later)
To run the provided build scripts.
JUnit Unit Testing Framework
(Version 3.4 or later)
To run the provided unit tests.


Release Info

Current Release: Release 2.0 Alpha 1

Planned Next Release: N/A


Committers

The following individuals are the primary developers and maintainers of this component. Developers who plan to use HTTP Client in their own projects are encouraged to collaborate on the future development of this component to ensure that it continues to meet a variety of needs.

  • Morgan Delagrange
  • B.C. Holmes
  • Costin Manolache
  • Remy Maucherat
  • Sung-Gu Park
  • Juergen Pill
  • Doug Sale
  • Rodney Waldhoff


Action Items

Like to help? The team has identified the following action items. To volunteer for a task, add your name to the list below, or send an email to commons-dev@jakarta.apache.org.

Action Item Volunteer(s)
Documentation Additional documentation is always welcome.  
Digest Authentication Add support for Digest authentication to the Authenticator class.  
RFC 2965 Support (Port sensitive cookies) RFC 2109 doesn't consider port numbers when matching and filtering cookies. RFC 2965 does. Modify the Cookie class so that it (optionally?) supports RFC 2965, while maintaining support for RFC 2109-style (portless) cookies.  
Cookie Ordering Per RFC 2109, the cookies returned in a Cookie header should be ordered so that the "better matches" (i.e., more specific path/domain) come first. Currently no effort is made to do that.  
Proxy Support Testing HTTP Client's proxy support has not been extensively tested. (There are no known issues either, but...). Test various HTTP Client features via a proxy, or even better, add a suite of unit/functional tests demonstrating the proxy functionality.  

Additional action items may be listed within source comments flagged by the strings FIXME or TODO.



Copyright © 1999-2001, Apache Software Foundation