Properly respond to Expect: 100-continue #43

New Issue

Jef Roosens · 2023-12-09T15:48:51+01:00

Jef Roosens commented

2023-12-09 15:48:51 +01:00

Libcurl sends this header with the idea that you verify whether the request will be accepted or not before the client starting sending any of the body data. While this definitely isn't necessary for the workings of the server, it might be cool to implement it anyways.

Jef Roosens added the

Kind/Feature

label 2023-12-09 15:48:51 +01:00

Jef Roosens commented

2023-12-10 12:33:04 +01:00

Poster

For this to work, we might need to introduce the concept of a validator function that is called after the request has been parsed, but before any of its body data has been read. This function would then decide, based no the request head alone, whether we want to proceed with the given request or not. This could then transparently respond to the 100-continue.

For this to work, we might need to introduce the concept of a validator function that is called after the request has been parsed, but before any of its body data has been read. This function would then decide, based no the request head alone, whether we want to proceed with the given request or not. This could then transparently respond to the `100-continue`.

Jef Roosens added the

Project/Lander

label 2024-08-26 10:40:20 +02:00

Sign in to join this conversation.