#36397: Server ignores 'Last-Modified' date (Debian#926074)
-------------------------------------+-------------------------------------
Reporter: Christian Buhtz | Owner: (none)
Type: Bug | Status: closed
Component: contrib.syndication | Version: 4.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* cc: Colin Watson (added)
* component: Uncategorized => contrib.syndication
* resolution: => invalid
* status: new => closed
* type: Uncategorized => Bug
* version: => 4.2
Comment:
Hello Christian Buhtz, thank you for taking the time to create this
ticket. I see from the messages in the Debian mailing list that you care
deeply about this issue. Still, this is not an issue in Django: the `Feed`
implementation from the syndication framework does handle item publication
as shown in the Django source code. See the `class Feed` implementation at
[https://github.com/django/django/blob/main/django/contrib/syndication/views.py#L35-L49
these relevant lines]. This behavior is enabled via
`ConditionalGetMiddleware` (which I'm not sure if the Debian tracker
uses).
The issue you're experiencing could be caused by a variety of factors,
including (but not limited to) the `PackageNewsFeed` view (from the
[https://salsa.debian.org/qa/distro-
tracker/-/blob/master/distro_tracker/core/news_feed.py?ref_type=heads#L101-106
Debian source code that defines item_pubdate()]) returning timezone-naive
datetimes or `None`.
Considering that this issue tracker is meant to track confirmed bugs in
Django itself, and since this report seems to stem from application-
specific code in the Debian project, I’ll close this ticket as `invalid`
per our [https://docs.djangoproject.com/en/dev/internals/contributing
/triaging-tickets/#closing-tickets ticket triaging process]. The best
place to get further help would be one of the support forums listed at
[https://docs.djangoproject.com/en/dev/faq/help/#how-do-i-do-x-why-
doesn-t-y-work-where-can-i-go-to-get-help this link]. If after debugging,
you (or someone else) find that the problem lies in Django itself, please
reopen the ticket with specific details and, ideally, a minimal Django
project or failing test case that demonstrates the issue (using Django
code only, we're not able to debug arbitrary third-party services).
--
Ticket URL: <https://code.djangoproject.com/ticket/36397#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070196d41e30f9-42f7e74d-fad4-4ef5-bf6a-f29ce3a18f10-000000%40eu-central-1.amazonses.com.
