Which protocol/version is NOT supported by the HTTP connector?

Prepare for the MuleSoft Integration Architect exam. Study with flashcards and multiple-choice questions, each offering hints and explanations to deepen understanding. Ace your exam with our focused preparation tools!

Multiple Choice

Which protocol/version is NOT supported by the HTTP connector?

Explanation:
The HTTP connector in MuleSoft works with HTTP/1.x traffic. It natively supports HTTP/1.0 and HTTP/1.1 for both inbound (listeners) and outbound calls, including receiving inbound requests over HTTP or HTTPS (TLS-enabled). HTTP/2 introduces different semantics—multiplexing, binary framing, and header compression—that the connector does not implement directly, so HTTP/2 is not supported natively. If you need HTTP/2, you’d typically place a gateway or reverse proxy in front of Mule that terminates HTTP/2 and forwards to Mule as HTTP/1.1.

The HTTP connector in MuleSoft works with HTTP/1.x traffic. It natively supports HTTP/1.0 and HTTP/1.1 for both inbound (listeners) and outbound calls, including receiving inbound requests over HTTP or HTTPS (TLS-enabled). HTTP/2 introduces different semantics—multiplexing, binary framing, and header compression—that the connector does not implement directly, so HTTP/2 is not supported natively. If you need HTTP/2, you’d typically place a gateway or reverse proxy in front of Mule that terminates HTTP/2 and forwards to Mule as HTTP/1.1.

More practice questions
Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy