Closed
Bug 566673
Opened 14 years ago
Closed 12 years ago
Atom feeds on http://hg.mozilla.org/ do not have etags or last-modified headers, wastes resources
Categories
(Developer Services :: Mercurial: hg.mozilla.org, defect)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: christian, Unassigned)
References
()
Details
I have a script that reads the RSS feeds on http://hg.mozilla.org. I want to respect etags and last-modified so that I don't hammer the server yet can have data that is reasonably up to date. It doesn't look like the server gives me the headers I need, here's a dump from python: {'date': 'Tue, 18 May 2010 18:43:24 GMT', 'transfer-encoding': 'chunked', 'connection': 'close', 'content-type': 'application/atom+xml; charset=UTF-8', 'server': 'Apache/2.2.3 (Red Hat)'} I want my script to check the etags and/or last-modified so it doesn't need to pull down the entire feed to see if anything has changed.
Updated•14 years ago
|
Assignee: server-ops → aravind
It looks like the build system polls and could be enhanced if etag/last-modified was available (http://hg.mozilla.org/build/buildbotcustom/file/8b1380cbf092/changes/hgpoller.py)
Comment 2•14 years ago
|
||
I think you should file this upstream with Mercurial: http://mercurial.selenic.com/bts/ Those feeds are generated by hgweb, which is part of Mercurial. We don't have any customization of them.
Looks like it is already at http://mercurial.selenic.com/bts/issue1845
Comment 4•14 years ago
|
||
Upstream bug, will pick up when we update hg.
Assignee: aravind → nobody
Component: Server Operations → Hg: Customizations
QA Contact: mrz → hg.customizations
Comment 5•12 years ago
|
||
That upstream bug got fixed, and I see etag in the regular hgweb feeds, and the pushlog feeds now.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Assignee | ||
Updated•10 years ago
|
Product: Release Engineering → Developer Services
You need to log in
before you can comment on or make changes to this bug.
Description
•