Running Application with TLSSettings and Settings.
Modulewarp-tls-3.4.13Haskell2010
Network.Wai.Handler.WarpTLS
HTTP over TLS support for Warp via the TLS package.
If HTTP/2 is negotiated by ALPN, HTTP/2 over TLS is used. Otherwise HTTP/1.1 over TLS is used.
Support for SSL is now obsoleted.
- 4 types
- 21 values
- Packagewarp-tls-3.4.13
- Exports25
- LanguageHaskell2010
- LicenceMIT
- SourceWarpTLS.hs
Runner
2 declarationsRunning Application with TLSSettings and Settings using specified Socket.
Settings
2 declarationsSettings for WarpTLS.
Default TLSSettings. Use this to create TLSSettings with the field record name (aka accessors).
Smart constructors
0 declarationsFrom files
A smart constructor for TLSSettings based on defaultTlsSettings.
value
tlsSettingsChain :: FilePathCertificate file
-> [FilePath]Chain certificate files
-> FilePathKey file
-> TLSSettings
A smart constructor for TLSSettings that allows specifying chain certificates based on defaultTlsSettings.
Since 3.0.3
From memory
A smart constructor for TLSSettings, but uses in-memory representations of the certificate and key based on defaultTlsSettings.
Since 3.0.1
value
tlsSettingsChainMemory :: ByteStringCertificate bytes
-> [ByteString]Chain certificate bytes
-> ByteStringKey bytes
-> TLSSettings
A smart constructor for TLSSettings, but uses in-memory representations of the certificate and key based on defaultTlsSettings.
Since 3.0.3
From references
value
tlsSettingsRef :: IORef ByteStringReference to certificate bytes
-> IORef ByteStringReference to key bytes
-> TLSSettings
Deprecated. This function was added to allow Warp to serve new certificates without restarting, but it has always behaved the same as tlsSettingsMemory. It will be removed in the next major release. To retain existing behavior, swich to tlsSettingsMemory. To dynamically update credentials, see tlsSettingsSni.
A smart constructor for TLSSettings, but uses references to in-memory representations of the certificate and key based on defaultTlsSettings.
value
tlsSettingsChainRef :: IORef ByteStringReference to certificate bytes
-> [IORef ByteString]Reference to chain certificate bytes
-> IORef ByteStringReference to key bytes
-> TLSSettings
Deprecated. This function was added to allow Warp to serve new certificates without restarting, but it has always behaved the same as tlsSettingsChainMemory. It will be removed in the next major release. To retain existing behavior, swich to tlsSettingsChainMemory. To dynamically update credentials, see tlsSettingsSni.
A smart constructor for TLSSettings, but uses references to in-memory representations of the certificate and key based on defaultTlsSettings.
Determines where to load the certificate, chain certificates, and key from.
Instances1Show
Show CertSettingsDefined in warp-tls-3.4.13 · Network.Wai.Handler.WarpTLS.Internal
Dynamically retrieved
Smart constructor for TLS settings that obtains its credentials during Server Name Indication. Can be used to return different credentials depending on the hostname but also to retrieve dynamically updated credentials from an IORef. Credentials can be loaded from PEM-encoded chain and key files using credentialLoadX509.
Accessors
11 declarationsSpecifying Credentials directly. If this value is
specified, other fields such as certFile are ignored.
Since 3.2.12
The TLS versions this server accepts.
Since 1.4.2
The TLS ciphers this server accepts.
Since 1.4.2
Whether or not to demand a certificate from the client. If this is set to True, you must handle received certificates in a server hook or all connections will fail.
tlsWantClientCert defaultTlsSettingsFalse
Since 3.0.2
The server-side hooks called by the tls package, including actions to take when a client certificate is received. See the Network.TLS module for details.
Default: defaultServerHooks
Since 3.0.2
Configuration for ServerDHEParams
more function lives in crypton package
Default: Nothing
Since 3.2.2
Configuration for in-memory TLS session manager.
If Nothing, noSessionManager is used.
Otherwise, an in-memory TLS session manager is created
according to Config.
Default: Nothing
Since 3.2.4
Specifying SessionManager directly. If this value is specified, tlsSessionManagerConfig is ignored.
Since 3.2.12
Do we allow insecure connections with this server as well?
onInsecure defaultTlsSettingsDenyInsecure "This server only accepts secure HTTPS connections."
Since 1.4.0
An action when a plain HTTP comes to HTTP over TLS/SSL port.
Constructors
Instances1Show
Show OnInsecureDefined in warp-tls-3.4.13 · Network.Wai.Handler.WarpTLS.Internal
Exception
1 declarationInstances2Show, Exception
Show WarpTLSExceptionDefined in warp-tls-3.4.13 · Network.Wai.Handler.WarpTLSException WarpTLSExceptionDefined in warp-tls-3.4.13 · Network.Wai.Handler.WarpTLS
Low-level
1 declarationGet Connection and Transport for a TLS connection that is already did the handshake.
@since 3.4.7