META-INF.mule-https.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
A Mule transport for Http Connectivity. This transport supplies a simple Http Server implementation.
The newest version!



    
    
    
    

    
        
            The Secure 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 secure inbound, secure outbound, and secure polling HTTP endpoints. 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.
        
        
            HTTPS
            HTTPS Transport
            http
            
                
            
        
    

    
        
            
                This connector provides Secure HTTP connectivity on top of what is already provided with the Mule [HTTP Transport].
            
        
    

     
        
            
                Allows Mule to poll an external HTTP server and generate events from the result. This is useful for pull-only web services. This connector provides a secure version of the PollingHttpConnector.
            
        
    

    
        
            
                
                    
                        
                            
                                Configures the client key store with the following attributes:
                                * path: The location (which will be resolved relative to the current classpath and file system, if possible) of the keystore that contains public certificates and private keys for identification
                                * storePassword: The password used to protect the keystore
                                * class: The type of keystore used (a Java class name)
                            
                        
                    
                    
                        
                            
                                Configures the direct key store with the following attributes:
                                * path: The location (which will be resolved relative to the current classpath and file system, if possible) of the keystore that contains public certificates and private keys for identification
                                * class: The type of keystore used (a Java class name)
                                * keyPassword: The password used to protect the private key
                                * storePassword: The password used to protect the keystore
                                * algorithm: The algorithm used by the keystore
                            
                        
                    
                    
                        
                            
                                Configures the trust store. The attributes are:
                                * path: The location (which will be resolved relative to the current classpath and file system, if possible) of the trust store that contains public certificates of trusted servers
                                * storePassword: The password used to protect the trust store
                                * class: The type of trust store used (a Java class name)
                                * algorithm: The algorithm used by the trust store
                                * factory-ref: Reference to the trust manager factory
                                * explicitOnly: Whether this is an explicit trust store
                                * requireClientAuthentication: Whether client authentication is required
                            
                        
                    
                    
                        
                            
                                Configures the global Java protocol handler. It has one attribute, property, which specifies the java.protocol.handler.pkgs system property.
                            
                        
                    
                
            
        
    

    
        
            
                
                    
                        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 the request is empty, users can configure a content filter on the endpoint to filter these messages out.
                        
                    
                
            
        
    

    
        
            
                An inbound HTTPS endpoint exposes a service securely over HTTPS, essentially making it an HTTP server. If polling of a remote HTTP service is required, this endpoint should be configured with a polling HTTPS connector.
            
        
    
    
        
            
        
    

    
        
            
                The HTTPS outbound endpoint allows Mule to send requests securely using SSL to external servers or Mule inbound HTTP endpoints using HTTP over SSL protocol.
            
        
    
    
        
            
        
    

    
        
            
                Configures a global HTTPS endpoint that can be referenced by services. Services can augment the configuration defined in the global endpoint with local configuration elements.
            
        
    
    
        
            
        
    

    
        
            
                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'.