At this point, I was convinced that for some reason the Share Point is unable to either read the proxy or use the proxy to reach the internet.
For this, we create test application, which read the proxy settings from the web.config file using IIS site. At this time, we decide to open a premier case with MSFT and get the solutions.
For example, you can use the RSS Viewer Web Part to display information such as news and weather reports.
To display multiple RSS feeds, just add multiple instances of the Web Part to the page.
Highlight the affected web application and select General Settings from the ribbon.
Turning off web page security validation worked, but I was then unable to create any new sites or lists because I received the error “An unhandled exception occured in the Silverlight application Share Point 2010.
Having consulted Microsoft about this issue, I was pleased to hear that this has been recognised as a bug…….although it won’t be fixed until either June 2013 CU, or Service Pack 2 – whichever is released first.
We have had a site collection set up in Share Point 2010 where we added quite a few RSS feeds that showed content from other parts of the site collection.
So, initially we configured their proxy explicitly by adding this in the web.config file of the Share Point application. Socket Exception (0x80004005): No such host is known at System. When we upgraded the site collection to Share Point 2013 (with 2010 layout) all the RSS feeds stopped working.On our 'pure' 2013 test environment, I tried setting up an RSS-viewer that just showed an external RSS feed. It seems as if some kind of feature needs to be enabled in 2013 that wasn't needed in 2010?On the site collection feeding the RSS, I have checked that RSS is enabled on the site collection level.On the site collection receiving the RSS, I have checked that RSS is enabled on the site collection level.