HTTP 1.1 introduced the HTTP Status 100, also know as the Continue status. The purpose of the continue status is to allow a client that is sending a request to check to see if the server is willing to accept the request based on the Request Headers.
The client’s sends Expect: 100-Continue header with the request. The server evaluates the header and chooses to send the Status Code 100 if the message to be sent will be accepted by the server.
The IBM Social Business Toolkit’s Java libraries use the Apache Http Client, which uses the expect 100-Continue. This 100-Continue adds extra requests to the a single query, while light weight it can add a delay to the request.
Good news, you can disable it.
For J2EE Apps, navigate to your managed-beans.xml. Locate the Endpoint you want to disable it for, add a managed-property.
For Standalone Java Apps, you can add a property to your Endpoint declaration.
ConnectionsBasicEndpoint endpoint = new ConnectionsBasicEndpoint();
You’ve now avoided any performance impacts from Expected Continue – 100.
HTTP 1.1. Specification – Section 8 http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html
IBM Social Business Toolkit
Apache Http Client