-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
?
-
Not Needed
Related to the linked HELP ticket, this customer had a really large user object and we found that envoy was rejecting the request.
{"upstream_cluster":null,"resp_code":431,"resp_flags":"DPE","user-agent":null,"response_duration":null,"req_method":null,"x-request-id":null,"bytes_received":0,"bytes_sent":31,"upstream_host":null,"resp_code_details":"http1.headers_too_large","upstream-service-time":null,"start_time":"2024-07-08T16:30:19.642506447+0000","request_duration":null,"protocol":"HTTP/1.1","connection_termination_details":null,"response_tx_duration":null,"authority":null,"downstream_direct_remote_address":"188.24.22.213:56515","duration":51,"req_path":null,"client_ip":"188.24.22.213"}
This was not showing up in the logs in any discernable way according to the help ticket (here are the logs they posted) 01340259 error-1.rtf
It should be possible to repro this by using custom user data and making the object 1/2 MB (that is what the customer had it as).
The goal of this ticket would be to make sure that this is a clearer error in the logs ideally.
This was happening on this SDK release https://github.com/realm/realm-swift/releases/tag/v10.49.1 which correlates to Realm-Core 14.4.1
