Properly respond to Expect: 100-continue #43

Open
opened 2023-12-09 15:48:51 +01:00 by Jef Roosens · 1 comment

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.

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
feature
label 2023-12-09 15:48:51 +01:00

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`.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Chewing_Bever/lander#43
There is no content yet.