Skip to content

Commit eee1f7d

Browse files
committed
Changelog for #376.
1 parent 13cec89 commit eee1f7d

File tree

2 files changed

+13
-3
lines changed

2 files changed

+13
-3
lines changed

CHANGES.rst

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,13 @@ Version 3.21
1111

1212
Unreleased
1313

14+
* During :ref:`scheduled updates <scheduled>`,
15+
honor the Cache-Control max-age and Expires HTTP headers.
16+
(:issue:`376`)
17+
18+
* Also, if the Retry-After is a date,
19+
make the update interval relative to Date.
20+
1421

1522
Version 3.20
1623
------------

docs/guide.rst

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -289,9 +289,9 @@ such that updates don't happen exactly at the the same time;
289289
for example, with a one-hour interval, a jitter of 0.25 means
290290
updates will occur any time in the first 15 minutes of each hour.
291291

292-
If the server sends the Retry-After HTTP header with
293-
429 Too Many Requests or 503 Service Unavailable responses,
294-
:meth:`update_feeds(scheduled=True) <Reader.update_feeds>` will honor it.
292+
If the server responds with any of the
293+
Cache-Control max-age, Expires, or Retry-After HTTP headers,
294+
:meth:`update_feeds(scheduled=True) <Reader.update_feeds>` will honor them.
295295

296296

297297
.. note::
@@ -308,6 +308,9 @@ If the server sends the Retry-After HTTP header with
308308
.. versionchanged:: 3.15
309309
Honor the Retry-After HTTP header.
310310

311+
.. versionchanged:: 3.21
312+
Honor the Cache-Control max-age and Expires HTTP headers.
313+
311314

312315
Update status
313316
~~~~~~~~~~~~~

0 commit comments

Comments
 (0)