You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|[to-backend](to-backend)| How to secure communication from the API Gateway to a backend server. |
6
6
|[api-with-tls-pkcs12](api-with-tls-pkcs12)| How to protect APIs deployed on the Gateway with TLS certificates (using a keystore in the PKCS12 format)" |
7
-
|[api-with-tls-pem](api-with-tls-pem)| How to protect APIs deployed on the Gateway with TLS certificates (using PEM formatted files for the key and the certificate) |
7
+
|[api-with-tls-pem](api-with-tls-pem)| How to protect APIs deployed on the Gateway with TLS certificates (using PEM formatted files for the key and the certificate) |
8
+
9
+
# SSL/TLS Errors
10
+
Depending on your use case for Membrane API Gateway, you may or may not want to set `<ssl showSSLExceptions="false">` (default) or `<ssl showSSLExceptions="true">`.
11
+
12
+
In case you are setting up your keys and certificates for the first time, or you are searching for TLS misconfigurations,
13
+
we advise `<ssl showSSLExceptions="true">`. This is why all examples in this folder have this setting.
14
+
15
+
But when Membrane API Gateway is directly exposed to the internet on port 443, you most probably want to turn it off because too much "SPAM" is arriving.
0 commit comments