<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Fop2 not working since chrome version 36 update]]></title><description><![CDATA[<p dir="auto">Hi Guys,</p>
<p dir="auto">Fop2 has been working fine for our 200 customers but since the google chrome update to version 36 in the last couple days n-one can now access Fop2. The few computers that havnt automatically updated and are still on version 35 are working fine.</p>
<p dir="auto">Do you know if there will be an update so fop2 will work on Chrome version 36? or a fix? or other browsers that work fine?</p>
]]></description><link>http://localhost:4567/topic/1775/fop2-not-working-since-chrome-version-36-update</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 08:39:30 GMT</lastBuildDate><atom:link href="http://localhost:4567/topic/1775.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 21 Jul 2014 03:28:04 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Fop2 not working since chrome version 36 update on Thu, 24 Jul 2014 20:02:51 GMT]]></title><description><![CDATA[<p dir="auto">The last chrome update denies non secure websockets connections over https, so to fix it you have to disable websockets in fop2 (as you did), or upgrade to fop2 2.27 that includes support for secure websockets and configure the ssl certificates in fop2.cfg for it.</p>
]]></description><link>http://localhost:4567/post/7693</link><guid isPermaLink="true">http://localhost:4567/post/7693</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Thu, 24 Jul 2014 20:02:51 GMT</pubDate></item><item><title><![CDATA[Reply to Fop2 not working since chrome version 36 update on Mon, 21 Jul 2014 22:49:23 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">Thanks for your reply, we are also using MAC OSX but our latest version is only 36.</p>
<p dir="auto">I checked the file /var/www/html/fop2/js/presence.js and disablewebsocket was set to false so i set it to true and now its working fine.</p>
<p dir="auto">Thanks again.</p>
]]></description><link>http://localhost:4567/post/7692</link><guid isPermaLink="true">http://localhost:4567/post/7692</guid><dc:creator><![CDATA[rookie01]]></dc:creator><pubDate>Mon, 21 Jul 2014 22:49:23 GMT</pubDate></item><item><title><![CDATA[Reply to Fop2 not working since chrome version 36 update on Mon, 21 Jul 2014 20:08:56 GMT]]></title><description><![CDATA[<p dir="auto">I had other reports of issues with Chrome today. The problem is that I am using OSX, and my Chrome version is now 38.0.2960 and it works just fine. My suggestion for you is to enable or disable websockets in /var/www/html/fop2/js/presence.js , not sure if you have it enabled or not, in any case, change it so it uses the other mode (fop2 supports both flash xmlsockets and html5 websockets). Perhpas the chrome change affects one of those methods (for example flash), and not websockets, or viceversa.</p>
<p dir="auto">In any case, I have to see what Chrome version does windows have and check from there to find out myself, as the OSX version has a higher release number and works fine (With websockets at least).</p>
<p dir="auto">Also, be always sure to use the latest FOP2 release.</p>
]]></description><link>http://localhost:4567/post/7691</link><guid isPermaLink="true">http://localhost:4567/post/7691</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Mon, 21 Jul 2014 20:08:56 GMT</pubDate></item></channel></rss>