Configuring HTTP / RESTful Connectors

All GLU HTTP connectors use HTTP4 component.

HTTP4 is a new version of the Hypertext Transfer Protocol that aims to improve the performance, security, and scalability of web applications. It is based on the QUIC protocol, which uses UDP instead of TCP and supports multiplexing, encryption, and congestion control

HTTP Cross-Origin Resource Sharing

Host settings are the generic parts of the path e.g. http://localhost:9088/services

The Context Names configured in the Integration builder will result in a Outbound Connector Requests
that comprise the following parts: {host}{port}/{contextName}

Cross-Origin Resource Sharing (CORS) is an HTTP-header based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources.

To enable GLU CORS support, add ?enableCORS and allowed Headers to the Context Name in the Integration Builder.

1. Allow All Headers ?enableCORS=true&filterInit.allowedHeaders=*

2. Allow Specific Headers ?enableCORS=true&filterInit.allowedHeaders=x-channel-access-key,Access-Control-Allow-Headers,Access-Control-Allow-Methods,Access-Control-Allow-Origin

Properties

The Properties Tab is where Protocol specific Properties are defined. There are no HTTP or REST specific properties so these options are not applicable for such Connector types. For other types such for a SOAP Connector, the SOAP Properties such as WSDL Location, SOAP Context Service name etc. will be presented.