diff --git a/pages/serverless-containers/concepts.mdx b/pages/serverless-containers/concepts.mdx index 9844aa8025..0ee7c68906 100644 --- a/pages/serverless-containers/concepts.mdx +++ b/pages/serverless-containers/concepts.mdx @@ -285,3 +285,7 @@ Unit used to measure the resource consumption of a container. It reflects the am ## Protocol Serverless Containers supports **http1** (default) and **http2** (`h2c`). Use HTTP/2 if your container application is configured to listen for HTTP/2 requests, such as a **gRPC** service or a web server that uses HTTP/2 features like multiplexing, otherwise, HTTP/1 is recommended. + + +HTTP/1.0 is not supported. Refer to the [dedicated troubleshooting page](/serverless-containers/troubleshooting/http1-errors/) for more information. + diff --git a/pages/serverless-containers/faq.mdx b/pages/serverless-containers/faq.mdx index 339bcaf1d2..2ec0a4c28e 100644 --- a/pages/serverless-containers/faq.mdx +++ b/pages/serverless-containers/faq.mdx @@ -235,6 +235,10 @@ Serverless Containers support **http1** and **http2**. **http1** is enabled by d 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**. + +HTTP/1.0 is not supported. Refer to the [dedicated troubleshooting page](/serverless-containers/troubleshooting/http1-errors/) for more information. + + ### Why does my gRPC container not respond? Containers use **http1** by default, yet the gRPC protocol requires `http2`. You can upgrade the protocol to `http2` (`h2c`). diff --git a/pages/serverless-containers/reference-content/containers-limitations.mdx b/pages/serverless-containers/reference-content/containers-limitations.mdx index fa95fe9dbf..f20d8ccb60 100644 --- a/pages/serverless-containers/reference-content/containers-limitations.mdx +++ b/pages/serverless-containers/reference-content/containers-limitations.mdx @@ -82,6 +82,10 @@ Do not have your containers listen on these ports, as they are used by our servi **Not available:** Serverless products are designed to abstract away infrastructure management, to be easily scalable, and to be cost-efficient and simple. So dedicated IPs are not supported for this product. +### Protocols + +Serverless Containers support HTTP/1.1 and HTTP/2 connections. HTTP/1.0 is not supported. Refer to the [dedicated troubleshooting page](/serverless-containers/troubleshooting/http1-errors/) for more information on how to solve HTTP/1.0 issues. + ## Private Networks and Virtual Private Cloud (VPC) Refer to the [dedicated documentation](/serverless-containers/reference-content/containers-private-networks/) on VPC and Serverless Containers integration for more information. diff --git a/pages/serverless-containers/troubleshooting/http1-errors.mdx b/pages/serverless-containers/troubleshooting/http1-errors.mdx new file mode 100644 index 0000000000..25eccd9226 --- /dev/null +++ b/pages/serverless-containers/troubleshooting/http1-errors.mdx @@ -0,0 +1,21 @@ +--- +title: Solving HTTP/1.0 issues +description: This page provides solutions to issues encountered while using HTTP/1.0 with Scaleway Serverless Containers +tags: issues error protocol http1.0 http0.9 backwards compatibiliy +dates: + validation: 2025-08-25 + posted: 2025-08-25 +--- + +## Problem + +I get an `HTTP 426 Upgrade Required` error while using Serverless Containers. + +## Cause + +Scaleway Serverless Containers only supports **HTTP/1.1** and **HTTP/2**. Other protocols are not compatible. + +## Solutions + +- Send **HTTP/1.1** requests if you have control over the protocol to use when calling a Serverless Container. +- Deploy a layer in front of your container to translate HTTP/1.0 into HTTP/1.1. \ No newline at end of file diff --git a/pages/serverless-containers/troubleshooting/index.mdx b/pages/serverless-containers/troubleshooting/index.mdx index 57d519660d..b9add516cf 100644 --- a/pages/serverless-containers/troubleshooting/index.mdx +++ b/pages/serverless-containers/troubleshooting/index.mdx @@ -68,4 +68,5 @@ productIcon: ContainersProductIcon - [I am experiencing clock drift with my Serverless Containers](/serverless-containers/troubleshooting/container-clock-drift) - [I am experiencing DNS issues with my container](/serverless-containers/troubleshooting/known-dns-containers-errors/) - [I cannot access my container](/serverless-containers/troubleshooting/cannot-access-container/) + - [I get errors when using HTTP/1.0](/serverless-containers/troubleshooting/http1-errors/) diff --git a/pages/serverless-functions/concepts.mdx b/pages/serverless-functions/concepts.mdx index 15efbe299f..66f593adb0 100644 --- a/pages/serverless-functions/concepts.mdx +++ b/pages/serverless-functions/concepts.mdx @@ -126,6 +126,10 @@ Previously, Private Networks at Scaleway were zoned. Only resources from within While DHCP is built into all new Private Networks, it may not be automatically activated for older Private Networks. Check our [migration](/vpc/reference-content/vpc-migration/) documentation for more information. +## Protocol + +Serverless Functions support **HTTP/1.1** and **HTTP/2**. Other protocols are not supported. Refer to the [dedicated troubleshooting page](/serverless-functions/troubleshooting/http1-errors/) for more information. + ## Queue trigger A queue trigger is a mechanism that connects a function to a queue created with [Scaleway Queues](/queues/concepts/#scaleway-queues), and invokes the function automatically whenever a message is added to the queue. diff --git a/pages/serverless-functions/faq.mdx b/pages/serverless-functions/faq.mdx index 894fb46dcf..fb8c21d223 100644 --- a/pages/serverless-functions/faq.mdx +++ b/pages/serverless-functions/faq.mdx @@ -253,6 +253,10 @@ You cannot use Serverless Functions with Edge Services because there are no nati By design, it is not possible to guarantee static IPs on Serverless Compute resources. +### Which protocols are supported by Serverless Functions? + +Serverless Functions support **HTTP/1.1** and **HTTP/2**. Other protocols are not supported. Refer to the [dedicated troubleshooting page](/serverless-functions/troubleshooting/http1-errors/) for more information. + ### How can I attach Block Storage to a Serverless Function? Scaleway Serverless Functions do not currently support attaching Block Storage. These functions are designed to be diff --git a/pages/serverless-functions/reference-content/functions-limitations.mdx b/pages/serverless-functions/reference-content/functions-limitations.mdx index a6aa53ea91..5f02be24ee 100644 --- a/pages/serverless-functions/reference-content/functions-limitations.mdx +++ b/pages/serverless-functions/reference-content/functions-limitations.mdx @@ -64,6 +64,10 @@ Due to potential abuse (spam), no outbound traffic is allowed through following **Not available:** Serverless products are designed to abstract away infrastructure management, to be easily scalable, and to be cost-efficient and simple. So dedicated IPs are not supported for this product. +### Protocols + +Serverless Functions support **HTTP/1.1** and **HTTP/2**. Other protocols are not supported. Refer to the [dedicated troubleshooting page](/serverless-functions/troubleshooting/http1-errors/) for more information. + ## Private Networks and Virtual Private Cloud (VPC) Refer to the [dedicated documentation](/serverless-functions/reference-content/functions-private-networks/) on VPC and Serverless Functions integration for more information. diff --git a/pages/serverless-functions/troubleshooting/http1-errors.mdx b/pages/serverless-functions/troubleshooting/http1-errors.mdx new file mode 100644 index 0000000000..3c21bde815 --- /dev/null +++ b/pages/serverless-functions/troubleshooting/http1-errors.mdx @@ -0,0 +1,21 @@ +--- +title: Solving HTTP/1.0 issues +description: This page provides solutions to issues encountered while using HTTP/1.0 with Scaleway Serverless Functions +tags: issues error protocol http1.0 http0.9 backwards compatibiliy +dates: + validation: 2025-08-25 + posted: 2025-08-25 +--- + +## Problem + +I get an `HTTP 426 Upgrade Required` error while using Serverless Functions. + +## Cause + +Scaleway Serverless Functions only supports **HTTP/1.1** and **HTTP/2**. Other protocols are not compatible. + +## Solutions + +- Send **HTTP/1.1** requests if you have control over the protocol to use when calling a Serverless Function. +- Deploy a layer in front of your function to translate HTTP/1.0 into HTTP/1.1. \ No newline at end of file diff --git a/pages/serverless-functions/troubleshooting/index.mdx b/pages/serverless-functions/troubleshooting/index.mdx index 4147b590f7..3dc7d31c39 100644 --- a/pages/serverless-functions/troubleshooting/index.mdx +++ b/pages/serverless-functions/troubleshooting/index.mdx @@ -69,4 +69,5 @@ productIcon: FunctionsProductIcon - [I am experiencing timeout errors](/serverless-functions/troubleshooting/timeout-error) - [My function fails after trying too many times](/serverless-functions/troubleshooting/too-many-retries) - [I am experiencing clock drift with my Serverless Functions](/serverless-functions/troubleshooting/function-clock-drift) + - [I get errors when using HTTP/1.0](/serverless-functions/troubleshooting/http1-errors/)