META-INF.mule-http.xsd Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of mule-transport-http Show documentation
Show all versions of mule-transport-http Show documentation
A Mule transport for Http Connectivity. This transport supplies a simple Http Server implementation.
The newest version!
The HTTP transport provides support for exposing services over HTTP and making HTTP client requests from Mule services to external services as part of service event flows. Mule supports inbound, outbound, and polling HTTP endpooints. These endpoints support all common features of the HTTP spec, such as ETag processing, cookies, and keepalive. Both HTTP 1.0 and 1.1 are supported.
HTTP
HTTP Transport
Allows Mule to communicate over HTTP. All parts of the HTTP spec are covered by Mule, so you can expect ETags to be honored as well as keep alive semantics and cookies.
Allows Mule to poll an external HTTP server and generate events from the result. This is useful for pull-only web services.
The cookie specification to be used by this connector when cookies are enabled.
The proxy host name or address.
The password to use for proxy access.
The proxy port number.
The username to use for proxy access.
Whether the proxy authentication scheme is NTLM or not. This property is required in order to use the right credentials under that scheme. Default is false
Whether to support cookies.
The time in milliseconds to wait between each request to the remote HTTP server.
Whether the ETag header from the remote server is processed if the header is present.
Whether Mule should discard any messages from the remote server that have a zero content length. For many services a zero length would mean there was no data to return. If the remote HTTP server does return content to say that that the request is empty, users can configure a content filter on the endpoint to filter these messages out.
Built-in RestServiceWrapper can be used to proxy REST style services as local Mule components.
An error filter can be used to detect whether the response from the remote service resulted in an error.
If the payload of the message is to be attached as a URL parameter, this should be set to the parameter name. If the message payload is an array of objects that multiple parameters can be set to, use each element in the array.
These are parameters that must be available on the current message for the request to be successful. The Key maps to the parameter name, the value can be any one of the valid expressions supported by Mule.
These are parameters that if they are on the current message will be added to the request, otherwise they will be ignored. The Key maps to the parameter name, the value can be any one of the valid expressions supported by Mule.
The HTTP method to use when making the service request.
The service URL to use when making the request. This should not contain any parameters, since these should be configured on the component. The service URL can contain Mule expressions, so the URL can be dynamic for each message request.
A transformer that converts an HTTP response to a Mule Message. The payload may be a String, stream, or byte array.
Converts an HTTP response payload into a string. The headers of the response will be preserved on the message.
This transformer will create a valid HTTP request using the current message and any HTTP headers set on the current message.
This transformer will create a valid HTTP response using the current message and any HTTP headers set on the current message.
This transformer parses the body of a HTTP request into a Map.
Authenticate users via Basic authorization using standard HTTP headers.
The delegate-security-provider to use for authenticating. Use this element
in case you have multiple security managers defined in your configuration.
An inbound HTTP endpoint exposes a service over HTTP, essentially making it an HTTP server. If polling of a remote HTTP service is required, this endpoint should be configured with a polling HTTP connector.
The HTTP outbound endpoint allows Mule to send requests to external servers or Mule inbound HTTP endpoints using the HTTP protocol.
If a request is made using GET that responds with a redirectLocation header, setting this to true will
make the request on the redirect URL. This only works when using GET since you cannot automatically follow
redirects when perfroming a POST (a restriction according to RFC 2616).
If a request returns a status code greater or equal than 400 an exception will be thrown.
Configures a 'global' HTTP endpoint that can be referenced by services. Services can augment the configuration defined in the global endpoint with local configuration elements.
If a request is made using GET that responds with a redirectLocation header, setting this to true will
make the request on the redirect URL. This only works when using GET since you cannot automatically follow
redirects when perfroming a POST (a restriction according to RFC 2616).
If a request returns a status code greater or equal than 400 an exception will be thrown.
The user name (if any) that will be used to authenticate against.
The password for the user.
The host to connect to. For inbound endpoints, this should be an address of a local network interface.
The port number to use when a connection is made.
The path for the HTTP URL. It must not start with a slash.
The HTTP ContentType to use.
The HTTP method to use.
DEPRECATED: Use keepAlive attribute instead.
Controls if the connection is kept alive.
(As of 2.2.2) The request-wildcard-filter element can be used to restrict the request by applying wildcard expressions to the URL.
Serves up static content for use with http. (Since Mule 3.2)
The resource base for where documents are served up from.
The default file to sever when a directory is specified. The default value is 'index.html'.
Indicates the name of the cookie.It supports expressions
Indicates the value of the cookie. It supports expressions.
Indicates the domain scope of the cookie. It supports expressions.
Indicates the path scope of the cookie. It supports expressions.
Indicates the exact date/time when the cookie expires. It must be specified in the form "Wdy, DD Mon YYYY HH:MM:SS GMT".
Indicates, in seconds, the max age of the cookie.
A boolean to specify that the cookie communication should be limited to encrypted transmission. It's fault by default.
Sets the version of the cookie specification to which this cookie conforms.
Indicates that the response MAY be cached by any cache.
Indicates that all or part of the response message is intended for a single user and MUST NOT be cached by a shared cache.
Specifies that a cache MUST NOT use the response to satisfy a subsequent request without successful revalidation with the origin server.
The purpose of the no-store directive is to prevent the inadvertent release or retention of sensitive information.
When the must-revalidate directive is present in a response received by a cache, that cache MUST NOT use the entry after it becomes stale to respond to a subsequent request without first revalidating it with the origin server.
When the max-age cache-control directive is present in a cached response, the response is stale if its current age is greater than the age value given. If a response includes both an Expires header and a max-age directive, the max-age directive overrides the Expires header, even if the Expires header is more restrictive.
The Status Code of the HTTP response.
Continue
Switching Protocol
OK
Created
Accepted
Non-Authoritative Information
No Content
Reset Content
Continue
Partial Content
Multiple Choices
Moved Permanently
Found
See Other
Not Modified
Use Proxy
Temporary Redirect
Bad Request
Unauthorized
Payment Required
Forbidden
Not Found
Method Not Allowed
Not Acceptable
Proxy Authentication Required
Request Timeout
Conflict
Gone
Length Required
Precondition Failed
Request Entity Too Large
Request-URI too long
Unsupported Media Type
Requested Range Not Satisfiable
Expectation Failed
Internal Server Error
Not Implemented
Bad Gateway
Service Unavailable
Gateway Timeout
Multiple Choices
HTTP Version Not Supported
© 2015 - 2025 Weber Informatics LLC | Privacy Policy