Opened 6 years ago
Closed 5 years ago
#1043 closed defect (fixed)
Streaming dup SYN detection
| Reported by: | zzz | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.9.12 |
| Component: | streaming | Version: | 0.9.7.1 |
| Keywords: | Cc: | zab@… | |
| Parent Tickets: | Sensitive: | no |
Description
Check if we do a good job of detecting and discarding duplicate SYN packets. In eepsite logs it's easy to find multiple GETs for the same thing from the same dest, a few seconds apart. Are those due to browser retransmissions (meaning there's nothing we can do) or are we seeing two SYNs with the same conn ID, and treating them as two separate conns? Needs research. Maybe something is broken or maybe not.
If connections get cleaned up faster than they do now (see #1039 #1040 #1041 #1042) then the problem may get a lot worse, and we may need an additional lru cache for conn ids.
Subtickets
Change History (2)
comment:1 Changed 6 years ago by
| Cc: | zab@… added |
|---|
comment:2 Changed 5 years ago by
| Milestone: | 0.9.9 → 0.9.12 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Recently-closed connections tracked as of 0.9.12 with an LRU cache as described in OP.