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
Copy file name to clipboardExpand all lines: pages/serverless-containers/faq.mdx
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -173,15 +173,19 @@ For now, the `HEALTHCHECK` Docker directive has no impact on container readiness
173
173
174
174
## Network and storage
175
175
176
+
### Can I redirect all HTTP traffic to HTTPS?
177
+
178
+
Yes, you can [redirect every inbound HTTP connections to HTTPS](/serverless-containers/how-to/manage-a-container/#manage-a-deployment-from-the-scaleway-container-registry) by enabling **HTTPS connections only** in the **Security** tab of the **Advanced options** of your container.
179
+
176
180
### Can I whitelist the IPs of my containers?
177
181
178
182
Serverless Containers does not yet support Private Networks. However, you can use the Scaleway IP ranges defined at [https://www.scaleway.com/en/peering/](https://www.scaleway.com/en/peering/) on Managed Databases and other products that allow IP filtering.
179
183
180
184
### Which protocols are supported by Serverless Containers?
181
185
182
-
Serverless Containers use the **http1**protocol by default, but some services (e.g., gRPC) only support `http2`.
186
+
Serverless Containers support **http1** and **http2**. **http1**is enabled by default, but some services (e.g., gRPC) only support **http2**.
183
187
184
-
Protocol switching is available in the Console under the `Advanced options` section in the `Deployment` tab.
188
+
You can [modify the protocol](/serverless-containers/how-to/manage-a-container/#manage-a-deployment-from-the-scaleway-container-registry) used by your container from the **Requests tab** of the **Advanced options**.
0 commit comments