Documentation Center

Protocol providers

Archive Manager provides protocol registration so that you can configure the protocols you want to allow in the captured URLs. Archive Manager provides default implementations of protocol providers, or you can implement your own custom provider. You configure protocol providers by adding a <ProtocolProvider> element in the cd_archivemanager_conf.xml configuration file.

Archive Manager provides the following implementations of protocol providers:

RelaxedProtocolProvider (the default)
The com.tridion.archiving.http.protocol.RelaxedProtocolProvider creates a protocol that registers HTTPS calls on port 443 to com.tridion.util.ssl.RelaxedSSLProtocolSocketFactory.
You should use this protocol provider when you need to work with an Application Server that uses self-signed certificates. The protocol provider provides a custom StrictProtocolSocketFactory that is configured to trust your self-signed certificate.
NoProtocolProvider
The com.tridion.archiving.http.protocol.NoProtocolProvider is a protocol provider that returns null so that Archive Manager does not register any protocols.
You should use this protocol provider when you do not want Archive Manager to handle HTTPS calls in any specific way—protocol handling when archiving HTTPS Web sites is then defined by the Application Server on which Archive Manager is running. Archive Manager will therefore not to be able to archive HTTPS Web sites with self-signed certificates unless the Application Server where Archive Manager is running can handle the calls to HTTPS Web sites.
SSLProtocolProvider
The com.tridion.archiving.http.protocol.SSLProtocolProvider creates a protocol that registers HTTPS calls on port 443 to org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory to validate the identity of the HTTPS server.
You should use this protocol provider when you need to work with a Application Server that uses strongly signed certificates.