that is certainly not desirable, but I am guessing there is something
else wrong that caused that problem. either google doesn't like the
content type returned in the HTTP response
"application/rss+xml;charset=utf-8" or it had a problem parsing the xml
header information. either of those problems could be in Roller if we
aren't returning the proper headers or maybe google was just being
stupid for some reason.
i don't think that web urls should be expected to indicate their content
type via a file extension, that is the whole reason why we have the
"content-type" HTTP response header.
-- Allen
John Hoffmann wrote:
Actually - there is very clear evidence that Google is at least
sometimes crippled by Roller's lack of file exntensions:
http://www.google.com/search?hl=en&lr=&q=gaim+solaris&btnG=Search
Search result #7 is an rss page in Roller.
-John
David M Johnson wrote:
On May 3, 2006, at 4:49 PM, John Hoffmann wrote:
Yes, you hit on a pet peeve. Extensions for content type not
implementation.
When designing the JavaOne web site 5 years ago we made every page
available in 4 formats which was controlled by the extension.
standard ones:
javaone/2001/session-1234/detail.html (for desktop browser visitors)
javaone/2001/session-1234/detail.xml (for crawling by 3rd party
data harvesters)
two custom types:
javaone/2001/session-1234/detail.lite (for small screen devices)
javaone/2001/session-1234/detail.prt (for printing)
John, are you saying that you are for or against file extensions?
- Dave
