ICAP

I have released the latest bug fix release with the following changes:

• ICAP Header removal NPE This bugfix in the icap header removal area prevents a possible NPE that could appear due to wrong duplication detection.
• ICAP Message aggregation Handler enhancement. This enhancement will change the behavior of the IcapChunkAggregator handler in order to properly handle preview message with an IEOF (early termination) of the message body content. In case a preview message content is ended with an early termination indicator the IcapMessage will no longer indicate to be of type preview, since all the available message content is already present in the given message due to the early termination. This feature can be activated by using a designated constructor in order to be fully backwards compatible!
• Changed to docbkx maven plugin for the documentation generation.
• Updated Copyright to 2012Enjoy

It’s done,

After extensive and successful performance and stability testing we have created the first stable release for the java icap codec.
This is the first time that a independent java ICAP codec is available and production ready.

Please do not hesitate contacting us when you successfully implement and use this codec! If you experience stability, performance or bug issues please let us now so that we can continuously improve the codec.

BTW: The binaries are available on this site as download or in maven central

RC3 is out,

This is most likely the last RC before the initial 1.0.0 release!

In this release we have done serious stress and load testing added the squid integration test server as a code example and adhered to the ICAP Errata Encapsulated header exceptions. this exception states that:

• OPTIONS requests
• 100 Continue response
• 204 No Content response

Do not require to contain a Encapsulated header. This is of course a direct violation to the RFC section 4.4.1 but since many server and client implementations adhere to this we decided to go with the flow……

Hi All,

We are currently testing the release candidate RC2 with a special stress test setup and will be soon ready to release the first full release of the ICAP codec. It is humbling to see how much traffic you all produce on our website. I have a feeling that this codec will be used in a lot of interesting products.

If you are planning or already using this codec and you wish to let us know how important this codec is for your application or product. Please send us an message via our contact form.
This will help to support this product and states the importance of it. And of course will make us proud

The Release Candidate 1.0.0.RC2 is out. We have made minor modifications to the IcapMessage class, added missing IcapHeader names and fixed a possible NPE in the simple example.

Hi All,

The first official release candidate is available at sonatypes repository.
Enjoy the release and feedback to us if you have problems with it.

Hi all,

We have successfully integration tested our icap codec against the Squid web proxy Cache version 3.1.6 client. this shows how good this implementation of the icap protocol is. Squid’s icap client is known to be very precise and only a good icap codec implemenation can communicate with this client without any problems.

This is another important step to release worthiness of this product.

We are soon coming to an end with the initial development of a JBoss Netty Codec which will enable Netty to handler ICAP as a server and client.