Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Atom 1.0 feed #12

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add Atom 1.0 feed #12

wants to merge 1 commit into from

Conversation

cernekee
Copy link

The current rss.js code always embeds non-SSL (http:) links in the feed data. This is not a good thing because in typical acralyzer installations, access to the bug reports requires transmitting the CouchDB administrator login/password over the wire. Also, crash reports may contain sensitive user data.

I experimented with adding SSL autodetection to rss.js, but encountered the following limitations:

  • The Netscape RSS 0.91 spec discourages (if not disallows) protocols other than http: and ftp:.
  • RSS does not support relative URLs at all.
  • CouchDB does not seem to give us an indication of whether SSL was used to access the current document, so we would have to "guess" (or maybe put it in a configuration file somewhere).

All three problems can be addressed by using Atom instead, and specifying relative URLs in the feed. So I am submitting atom.js, accessed via https://HOST/acra-PROJECT/_design/acra-storage/_list/atom/recent-items?descending=true. i.e. just replace "rss" with "atom" in the URL.

The output from this code passes the w3c.org feed validator. There is one non-fatal warning regarding the use of relative URLs in the "self" link, which is allowed but discouraged.

atom.js incorporates @halkeye's pending fixes from bug #10.

See here for background discussion on the CouchDB list; there are additional posts in the thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant