Details
-
Task
-
Resolution: Done
-
L3 - Default
-
None
-
None
-
Not defined
Description
Context:
We recently saw some event ingestion batches to fully completing and ending with a HTTP 100 status. Turns out curl which we use as client in the event ingestion pipeline by default uses the "Expect: 100-continue" header to first verify if the server would accept the payload.
We don't know yet why some batches just ended with the 100 code instead of curl sending the actual payload but we figured that it's not worth having this extra round-trip overhead in our nightly performance tests and thus want to disable that behavior, also see https://gms.tf/when-curl-sends-100-continue.html .
AT:
- the curl invocations that ingest event data to optimize have the 100 expect behavior disabled