HTTP / RESTful Connectors

Configuring HTTP / RESTful Connectors

All GLU HTTP connectors uses the HTTP4 component, which is a newer version of the Hypertext Transfer Protocol designed to enhance the performance, security, and scalability of web applications. It is built on the QUIC protocol, utilising UDP instead of TCP and supporting multiplexing, encryption, and congestion control.

HTTP Cross-Origin Resource Sharing

HTTP Cross-Origin Resource Sharing (CORS) is a mechanism in HTTP headers that enables a server to specify which origins, including domains, schemes, or ports, are allowed to access its resources. This is particularly important for web applications that need to interact with resources hosted on different domains.

In the context of GLU, where HTTP connectors are used, CORS support can be enabled to facilitate cross-origin requests. Here’s how you can configure CORS support in GLU:

  1. Host Settings: Host settings represent the generic parts of the URL path, such as http://localhost:9088/services.
  2. Context Names: Context names, configured in the Integration Builder, form the basis of outbound connector requests. These names typically include the host, port, and context name, resulting in a URL structure like {host}{port}/{contextName}.
  3. Enabling CORS: To enable CORS support in GLU, add ?enableCORS along with allowed headers to the context name in the Integration Builder. This informs the server that cross-origin requests should be permitted from specified origins. There are two common configurations for CORS support:
  • Allow All Headers: Use ?enableCORS=true&filterInit.allowedHeaders=* to allow all headers from any origin.
  • Allow Specific Headers: Alternatively, specify specific headers to be allowed using ?enableCORS=true&filterInit.allowedHeaders= followed by a comma-separated list of header names.

By configuring CORS support in GLU, you ensure that your HTTP connectors can effectively handle cross-origin requests, thereby enabling seamless interaction between different domains and resources.


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.

Was this article helpful?

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Support
Fill the form and we’ll contact you shortly

    I agree with

    We uses cookies to make your experience on this website better. Learn more
    Accept cookies