Replies: 1 comment 3 replies
-
|
An HTTP request can only have one status code in its response. While it's technically possible to send more than one, most clients and libraries will only consider the first one and ignore the rest. |
Beta Was this translation helpful? Give feedback.
-
|
I agree that most clients and libraries will only consider the first one and ignore the rest but based on RFC9110 I think this behavior is incorrect for 1XX responses since a 1XX is an interim response code and not a final response code. Ideally it would be good to get data for RFC9110: https://www.rfc-editor.org/rfc/rfc9110.html#name-informational-1xx |
Beta Was this translation helpful? Give feedback.
-
|
I checked the RFC again - you’re right. And yes, I think the correct behavior for the agent is to capture the final response code. Could you please create an issue for that? Though I’m not sure it’ll be easy to implement at the eBPF level |
Beta Was this translation helpful? Give feedback.
-
|
Created, coroot/coroot-node-agent#220 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have an application that is initially sending a 100 status code response to an HTTP request. A 200 status code is sent after the 100 but I only see the 100 status response in the Coroot traces. I need to know the latency of the 200 response and have little interest in the 100 response. Does the Coroot agent only return the first status response. If so can this be fixed to return the final response code?
Beta Was this translation helpful? Give feedback.
All reactions