[ 
https://issues.apache.org/jira/browse/ROL-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-933.
--------------------------

    Resolution: Won't Fix

I recently removed the Referrer information being collected by Roller (except 
in the case for blog comments) in favor of 3rd party solutions like Google 
Analytics but didn't realize this potential use case for it.  However, looking 
at the previous implementation it was never collecting user agent information 
anyway.

I've tested Roller trunk against both Chrome and Firefox with both the RSS and 
Atom feeds, and the problem you reported here in 2005 is thankfully not 
occurring anymore.

If there's significant demand for user agent info, perhaps we can implement 
this in the future.  Still, problems such as those you note would occur across 
most or all Roller installations, so it would be good to code Roller to fix 
these matters for all installations; also, thankfully, the front-end scripting 
frameworks today are usually quite capable of accommodating various browser 
quirks, making actions on our part less and less necessary.

> Include certain request data in RSS templates
> ---------------------------------------------
>
>                 Key: ROL-933
>                 URL: https://issues.apache.org/jira/browse/ROL-933
>             Project: Apache Roller
>          Issue Type: Improvement
>          Components: Newsfeeds (RSS & Atom)
>    Affects Versions: 2.0
>            Reporter: Matthew Schmidt
>            Assignee: Roller Unassigned
>
> In order to provide support for various browser specific problems, we should 
> have access to things like headers or user agents.  My primary concern is 
> getting the user-agent in the RSS feeds to change the content-type that is 
> served.  Firefox does not recognize application/rss+xml as a valid 
> displayable type, so it tries to open the url.  The problem is described here:
> http://www.petefreitag.com/item/381.cfm
> At minimum, I believe the user-agent in the context will get me where I need 
> to go.  But more information may be useful to others.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to