#20535: A 304 "Not Modified" should update the time to when we next expect a
modification
------------------------------+--------------------------------
Reporter: teor | Owner:
Type: defect | Status: new
Priority: Medium | Milestone: Tor: 0.2.9.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Keywords: regression
Actual Points: | Parent ID:
Points: 0.5 | Reviewer:
Sponsor: |
------------------------------+--------------------------------
In #20499, we discovered that when a 304 "Not Modified" is received,
relays try too hard when 09a0f2d0b is reverted, and don't try enough when
it is applied.
Instead, we should retry when we next expect the document to be modified.
And if we don't know, we should retry on some sensible schedule.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20535>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
