{ "attachments": [], "comments_archived": true, "date": "2003-07-23T21:00:37.000Z", "layout": "post", "title": "HTTP/1.1 From header and FOAF use in RSS aggregators", "wordpress_id": 448, "wordpress_slug": "from-foaf-rss", "wordpress_url": "http://www.decafbad.com/blog/?p=448", "year": "2003", "month": "07", "day": "23", "isDir": false, "slug": "from-foaf-rss", "type": "entry", "postName": "2003-07-23-from-foaf-rss", "html": "
Privacy issues aside (for the moment), there is a request header called \"FROM\", RFC 2616 s14.22 describes it. \n\n\n\n\n

Now, it does say it should, if given, contain an Internet e-mail address for the human user who controls the requesting user agent. SHOULD isn't MUST though, so what putting the user's homepage there?

\n

It also says \"In particular, robot agents SHOULD include this header so that the person responsible for running the robot can be contacted if problems occur on the receiving end.\"

\n
Source: eric scheid: Atom aggregator behavior (HTTP level) [dive into mark]\n\n
\n\n

Ask a stupid question , get a smart answer .

\n\n
<p>Last year, I thought it was a good idea to <a href=\"http://www.decafbad.com/blog/tech/old/oooahe.html\">abuse referers</a> in order to leave footprints behind when I consume <span class=\"caps\">RSS</span> feeds.  Then, this past January, the abuse in the practice was revealed and <a href=\"http://www.decafbad.com/blog/tech/old/ooodoe.html\">using the User-Agent header</a> was recommended for this.</p>\n\n<p>So, just for the hell of it, I <a href=\"http://diveintomark.org/archives/2003/07/21/atom_aggregator_behavior_http_level.html#c003136\">asked about the User-Agent header</a> for use in the context over at <a href=\"http://www.diveintomark.org\">Mark&#8217;s place</a> to see what responses I&#8217;d get.  The one that seemed most informative was from <a href=\"http://IAwiki.net/EricScheid\">Eric Scheid</a> as quoted above, referring me to <a href=\"http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.22\">the <span class=\"caps\">HTTP</span>/1.1 spec, section 14.22</a></p>\n\n<p>As per Eric&#8217;s comment and the spec, the value of a &#8220;From&#8221; header <span class=\"caps\">SHOULD</span> be an email address, but I would think that using a <span class=\"caps\">URL</span> wouldn&#8217;t be <strong>too</strong> much an abuse of this header.  Seems like a good idea to stick either the <span class=\"caps\">URL</span> to a blog here, or even better, stick the <span class=\"caps\">URL</span> to your <span class=\"caps\">FOAF</span> file here.</p>\n\n<p>I&#8217;d really like to see this get built into aggregators as an option, though not turned on by defauilt for privacy&#8217;s sake.  I like the idea of leaving my name or a trail back to me at the doorstep of people whose feeds I&#8217;m reading, and I like the idea of standardizing the practice as cleanly as possible.  Using the &#8220;From&#8221; header seems to be the best option so far, versus header abuse and User-Agent overloading.</p>\n\n<p>Man.  One of these days, I really have to get around to studying those specs in full, rather than just sporadically referencing them.  Thank goodness for smart guys like <a href=\"http://www.diveintomark.org\">Mark</a> and <a href=\"http://IAwiki.net/EricScheid\">Eric</a> (among others) who actually take the time to read these things and try to communicate the gist to the rest of us busy developers!</p>\n
\n\n\n\n

shortname=from_foaf_rss

\n

Archived Comments

\n\n\n\n
\n\n\n", "body": "
Privacy issues aside (for the moment), there is a request header called \"FROM\", RFC 2616 s14.22 describes it. \r\n\r\n

\r\nNow, it does say it should, if given, contain an Internet e-mail address for the human user who controls the requesting user agent. SHOULD isn't MUST though, so what putting the user's homepage there?\r\n\r\n

\r\nIt also says \"In particular, robot agents SHOULD include this header so that the person responsible for running the robot can be contacted if problems occur on the receiving end.\"
Source: eric scheid: Atom aggregator behavior (HTTP level) [dive into mark]
\t

Ask a stupid question , get a smart answer .

\r\n\r\n\t

Last year, I thought it was a good idea to abuse referers in order to leave footprints behind when I consume RSS feeds. Then, this past January, the abuse in the practice was revealed and using the User-Agent header was recommended for this.

\r\n\r\n\t

So, just for the hell of it, I asked about the User-Agent header for use in the context over at Mark’s place to see what responses I’d get. The one that seemed most informative was from Eric Scheid as quoted above, referring me to the HTTP/1.1 spec, section 14.22

\r\n\r\n\t

As per Eric’s comment and the spec, the value of a “From” header SHOULD be an email address, but I would think that using a URL wouldn’t be too much an abuse of this header. Seems like a good idea to stick either the URL to a blog here, or even better, stick the URL to your FOAF file here.

\r\n\r\n\t

I’d really like to see this get built into aggregators as an option, though not turned on by defauilt for privacy’s sake. I like the idea of leaving my name or a trail back to me at the doorstep of people whose feeds I’m reading, and I like the idea of standardizing the practice as cleanly as possible. Using the “From” header seems to be the best option so far, versus header abuse and User-Agent overloading.

\r\n\r\n\t

Man. One of these days, I really have to get around to studying those specs in full, rather than just sporadically referencing them. Thank goodness for smart guys like Mark and Eric (among others) who actually take the time to read these things and try to communicate the gist to the rest of us busy developers!

\r\n\r\nshortname=from_foaf_rss\r\n\r\n
\r\n

Archived Comments

\r\n \r\n \r\n \r\n
\r\n ", "parentPath": "./content/posts/archives/2003", "path": "2003/07/23/from-foaf-rss", "summary": "Privacy issues aside (for the moment), there is a request header called \"FROM\", RFC 2616 s14.22 describes it. \n\n\n\n\nNow, it does say it should, if given, contain an Internet e-mail address for the human user who controls the requesting user agent. SHOULD isn't MUST though, so what putting the user's homepage there?\nIt also says \"In particular, robot agents SHOULD include this header so that the person responsible for running the robot can be contacted if problems occur on the receiving end.\"\nSource: eric scheid: Atom aggregator behavior (HTTP level) [dive into mark]\n\n\n\nAsk a stupid question , get a smart answer .\n\n

Last year, I thought it was a good idea to abuse referers in order to leave footprints behind when I consume RSS feeds. Then, this past January, the abuse in the practice was revealed and using the User-Agent header was recommended for this.

\n\n

So, just for the hell of it, I asked about the User-Agent header for use in the context over at Mark’s place to see what responses I’d get. The one that seemed most informative was from Eric Scheid as quoted above, referring me to the HTTP/1.1 spec, section 14.22

\n\n

As per Eric’s comment and the spec, the value of a “From” header SHOULD be an email address, but I would think that using a URL wouldn’t be too much an abuse of this header. Seems like a good idea to stick either the URL to a blog here, or even better, stick the URL to your FOAF file here.

\n\n

I’d really like to see this get built into aggregators as an option, though not turned on by defauilt for privacy’s sake. I like the idea of leaving my name or a trail back to me at the doorstep of people whose feeds I’m reading, and I like the idea of standardizing the practice as cleanly as possible. Using the “From” header seems to be the best option so far, versus header abuse and User-Agent overloading.

\n\n

Man. One of these days, I really have to get around to studying those specs in full, rather than just sporadically referencing them. Thank goodness for smart guys like Mark and Eric (among others) who actually take the time to read these things and try to communicate the gist to the rest of us busy developers!

", "needsBuild": true, "prevPostPath": "2003/07/23/sleep-apnea", "prevPostTitle": "This evening's sleep brought to me by science.", "nextPostPath": "2003/07/26/amazon-rss", "nextPostTitle": "Finding the RSS in Amazon searches" }