From: Steve W. <sw...@pa...> - 2001-12-13 22:42:25
|
I would think RSS files should come out as text/plain. ~swain On Wed, 12 Dec 2001, Aredridel wrote: > > > > No, it's coming out as a gz file (my guess). I tried to look at it in Lynx > > and Lynx asked me if I wanted to download it (type oct/gz). > > Same for me. Galeon just displays it as if it were HTML. Any idea what the > content-type should be? > > Ari > --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa |
From: Aredridel <are...@nb...> - 2001-12-13 23:00:37
|
> > I would think RSS files should come out as text/plain. > > ~swain > After looking through all the URIs in my ~/.nautilus/news_channels.xml file, there seems to be a trend of using text/plain, text/xml, and one case of text/html among the sites. I bet that's what's keeping me from loading the rss into Nautilus. Aredridel |
From: Jeff D. <da...@da...> - 2001-12-14 05:17:50
|
On seemingly gzipped data: Currently, PhpWiki (1.3) uses PHP's ob_gzhandler() function to gzip-compress data sent to clients who send an 'Accept-Encoding: application/gzip' header in their request. When this happens, the fact that the data is compressed in indicated by a 'Content-Encoding' header in the response --- then the client/browser is supposed to uncompress the data before doing anything else with it. If you're seeing seemingly random (gzipped looking) binary data, then something is wrong with this process. (The RSS data is XML, and should look like something if you look at it with a text viewer.) ==== On viewing RSS with Galeon: Separate issue: Galeon treats all XML files as if they were 'text/xml'. It assumes they're marked up text, and tries to display the file as such. In the case of RSS, since none of the tags have any mark-up styles associated with them, what you see is the RSS file with all of the XML tags removed. As mentioned in my previous note, this will not make a lot of sense. |
From: Carsten K. <car...@ma...> - 2001-12-15 00:06:49
|
Thanks, you've answered my question too (even before I had a chance to ask it!) :-) My browser OmniWeb also downloads the RSS file as a gz archive. No problem with that, it just surprised me. Carsten On Friday, December 14, 2001, at 12:17 am, Jeff Dairiki wrote: > On seemingly gzipped data: > > Currently, PhpWiki (1.3) uses PHP's ob_gzhandler() function to > gzip-compress data sent to clients who send an 'Accept-Encoding: > application/gzip' header in their request. When this happens, the fact > that the data is compressed in indicated by a 'Content-Encoding' header in > the response --- then the client/browser is supposed to uncompress the > data before doing anything else with it. > > If you're seeing seemingly random (gzipped looking) binary data, then > something is wrong with this process. (The RSS data is XML, and should > look like something if you look at it with a text viewer.) |
From: Jeff D. <da...@da...> - 2001-12-14 04:56:54
|
On Thu, 13 Dec 2001 17:42:17 -0500 (EST) "Steve Wainstead" <sw...@pa...> wrote: > > I would think RSS files should come out as text/plain. > > ~swain According to the RSS 1.0 spec, it should be 'application/xml'. Makes sense to me: it's XML, so the choices are either 'application/xml' or 'text/xml'. (There are no registered MIME types especially for RDF or RSS.) If you strip the XML tags, what's left doesn't really make any sense to humans --- so 'application/xml' it is. See http://groups.yahoo.com/group/rss-dev/files/specification.html#s5 |
From: Carsten K. <car...@ma...> - 2001-12-15 00:01:54
|
My opinion is that PhpWiki's RSS should follow these three XML 1.0 recommendations (but I haven't yet checked whether it actually does or not) . 1. RSS files are written in XML, so text/xml or application/xml should be used: RFC 3023: XML Media Types <ftp://ftp.isi.edu/in-notes/rfc3023.txt> >If an XML document -- that is, the unprocessed, source XML document > -- is readable by casual users, text/xml is preferable to > application/xml. MIME user agents (and web user agents) that do not > have explicit support for text/xml will treat it as text/plain, for > example, by displaying the XML MIME entity as plain text. > Application/xml is preferable when the XML MIME entity is unreadable > by casual users. Similarly, text/xml-external-parsed-entity is > preferable when an external parsed entity is readable by casual > users, but application/xml-external-parsed-entity is preferable when > a plain text display is inappropriate. 2. It appears some RSS implementations omit the XML declaration line. I believe many XML readers will interpret this as incorrect XML. XML Declaration: <http://www.w3.org/TR/REC-xml#dt-xmldecl> > XML documents should begin with an XML declaration which specifies > the version of XML being used; the document type declaration must > appear before the first element in the document. 3. The XML declaration line must indicate the character set in use when unicode or UTF-8 is NOT being used. For example here is a declaration for an XML document encoded with ISO-8859-1: <?xml version="1.0" encoding='ISO-8859-1"?> Carsten On Thursday, December 13, 2001, at 05:42 pm, Steve Wainstead wrote: > > I would think RSS files should come out as text/plain. > > ~swain > > On Wed, 12 Dec 2001, Aredridel wrote: > >>> >>> No, it's coming out as a gz file (my guess). I tried to look at it in >>> Lynx >>> and Lynx asked me if I wanted to download it (type oct/gz). >> >> Same for me. Galeon just displays it as if it were HTML. Any idea what >> the >> content-type should be? >> >> Ari >> |