Good day team -

Trying to use/configure the RSS Reader webpart in an R2 SP1 site. The vAC site itself is accessed using HTTPS, but it appears that the RSS Reader doesn't and causes Internet Explorer to display the "Security Information", 'This page contains secure and non-secure items.' prompt.

How do we eliminate this? The customer has fallen in love with the RSS reader, but hates that prompt.

Thanks!
RickD

Rick,
i can't reproduce this behaviour, but i have tried with visionapp standard feeds:
visionapp News|http://www.visionapp.com/news-events/rss.xml;visionapp Forum|http://forum.visionapp.de/syndication.php?limit=50;Windows|http://www.microsoft.com/windowsvista/rss.xml

please post your feed config

Hey Daniel -

Is your vAC site being accessed with SSL? That's where we see the problem...

I'll find/upload some configs shortly. Thanks!
RickD

sure, vAC through https and RssFeeds through http...

cheers
Daniel

I think I know what causes this...

The feeds are retrieved on the backend side, so generally there's no problem of retrieving them as the backend is not restricted by the security settings of the browser.
But as soon as a feed contains links/images or any other content that points to an http source that content will be rendered into the browser which then throws the error message you're seeing.

So the only way to make sure you don't get such messages is to check the feeds for their content and, if in control, remove any non-plain-text content.
If not in control, the only way is to tinker with the security settings of the browser...

I figured this one out - one of my RSS sources was not exposed/linked by an XML file: it was an HTML page. I removed that one and life was good.

The problem/situation you reference above could be problematic though. Is it common for people to put graphics, etc. in RSS feeds?

For blogs it's already pretty common to put rich content in their feeds, most of the newspapers though still use only text and some markup.
So I'd say right now the situation is relaxed but it will probably become a problem in the near future.
http://www.engadget.com/ is a popular example.