[SERVER-56392] Don't allow clients to change the value of internalClient after the initial request Created: 27/Apr/21 Updated: 05/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Huayu Ouyang | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sa-remove-fv-backlog-22 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||
| Sprint: | Repl 2021-06-28, Service Arch 2022-10-17, Service Arch 2022-10-31, Service Arch 2022-11-14, Service Arch 2022-11-28 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 58 | ||||||||||||
| Description |
|
Currently, a client connection could send an initial hello/ismaster request without the internalClient field, and then later on send a subsequent hello command with internalClient: 1 specified, and the server would start treating this connection as an internal client connection. We should change this so that the server does not allow a connection to change the value of internalClient after it has already sent the initial hello/ismaster request. |