RSS Ticker - problems with proxy exception?

Get Help
1

Hi,

I have a proxy for connection to the internet, but intranet pages have to be accessed without proxy. Therefore I have a list of (sub)domains in the proxy_exceptions.
But it seems that the RSS feeds are only displayed when the source is in the internet.
Can it be that SimplePie has a problem here?

I’m asking because no matter what I define in proxy_exceptions, I get this log output:

755
17-01-02 04:29:50
CMS
Feed Error: This XML  document is invalid, likely due to invalid characters. XML error: SYSTEM or PUBLIC, the URI is missing at line 12, column 48

754
17-01-02 04:29:50
CMS
Config
isProxyException
***.net
in localhost,***.com,***.com,***.net,10.20.0.0/16,127.0.0.1,***.com,***.com,***.com.
Pos = 

753
17-01-02 04:29:50
CMS
Loading SimplePie to  handle RSS parsing.http://***.net/statusnet/index.php/api/statuses/public_timeline.rss?count=8

Actually my host should find a match in the proxy exceptions list.
Are you aware of any bug here?

Thanks a lot in advance for your help.

2

Hi Mondlicht,

Do you have, on your hostsystem where the CMS is runnng, in the systemkonfiguration Proxy-server enable and your Proxy exeptions write there?

Greetings Torsten

3

Hi Thorsten,

I fixed the problem by correctly setting the proxy and exceptions in the gnome system settings and removing the proxy from the xibo server configuration.

Thanks for the hint.

4

Cool. Nice to hear that my hint helps you!

5

Well… after some playing around, it seems that the twitter api doesn’t get the system configured proxy. The rest seems to work. Somehow strange I think.

6

It seems I am back at my original problem.
When configuring only the system proxy in the gnome settings, the proxy is not being used at all.
When configuring only the proxy in the xibo server settings, the proxy_exceptions are not correctly used, as described in the first post.
When configuring the proxy with exceptions both in the system and xibo settings, it’s the same as with only the xibo settings.

My host system is Debian Wheezy, if this is of interest.

7

I finally managed to get the proxy exceptions list working. stripos doesn’t work here. I put the exceptions into an array and checked each entry.

public static function isProxyException($host)
{
$strippedHost=parse_url($host,1);
//$strippedHost=$host;       
$proxyException = Config::GetSetting('PROXY_EXCEPTIONS');
$proxyExceptionArray = explode(',', $proxyException);
foreach ($proxyExceptionArray as $proxyExceptionArrayEntry){
    if (stripos($strippedHost, $proxyExceptionArrayEntry) !== false)
    {
        Debug::Audit($strippedHost . ' in ' . $proxyException . '. Included in: ' . $proxyExceptionArrayEntry);                
        return (true);
    }    

}
    //Debug::Audit($strippedHost . ' in ' . $proxyException . '. Pos = ' . stripos($strippedHost, $proxyException));

    return (false);
}
8

Still I have issues with the Twitter module and the proxy. Somehow the extra header defined in twitter.module.php (CURLOPT_HTTPHEADER) gets overwritten in a way that even Wireshark doesn’t decode it correctly.
…more things to be analyzed in the next days…

9

Opened a separate topic for the Twitter Proxy issue.

1 Like