Properly respond to Expect: 100-continue #43
Labels
No labels
Kind/Bug
Kind/Enhancement
Kind/Feature
Project/Lander
Project/Landerctl
idea
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Chewing_Bever/lander#43
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
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.