<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Safari, you&#8217;re dead to me now</title>
	<atom:link href="http://randommaccess.com/2007/11/safari-youre-dead-to-me-now/feed/" rel="self" type="application/rss+xml" />
	<link>http://randommaccess.com/2007/11/safari-youre-dead-to-me-now/</link>
	<description>Mac opinion. Punditry. Whatever.</description>
	<lastBuildDate>Thu, 24 Sep 2009 14:57:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Harry</title>
		<link>http://randommaccess.com/2007/11/safari-youre-dead-to-me-now/comment-page-1/#comment-12</link>
		<dc:creator>Harry</dc:creator>
		<pubDate>Wed, 21 Nov 2007 03:45:10 +0000</pubDate>
		<guid isPermaLink="false">http://randommaccess.com/2007/11/19/safari-youre-dead-to-me-now/#comment-12</guid>
		<description>Fair enough - and I can fully understand the feelings -- a large, entertainment and media based client of mine (really big) has a firewall making it impossible for iTunes to either grab album art, or get the radio stations list -- even though that&#039;s just regular http traffic.

Additionally, on the even of them launching their content being made available via iTunes, which was a big deal company wide, their firewall wouldn&#039;t even allow the iTunes store connection - &quot;not an approved application&quot;. That was fun.

On the other hand, Apple has worked diligently with me a while back in order to make Quicktime streaming work through the same firewall (with an exception in the QT code, just to accommodate that particular case). 

Oh yeah, and we&#039;re also talking about MS based firewalls :-(

I don&#039;t doubt that things have changed on Apple&#039;s end, that would cause this problem you&#039;re encountering, especially seeing as how Apple is pushing their reliance evangelical support of standards further with Leopard. One approach would be to work with your IT/network staff, though if they are MS-KoolAid drinkers, I see little hopes in any resolution from that end - though you may be surprised.

I&#039;ll check a bit on my end, along with some of my Apple relations, and dig up if there&#039;s any solution on the horizon, and let you know.</description>
		<content:encoded><![CDATA[<p>Fair enough &#8211; and I can fully understand the feelings &#8212; a large, entertainment and media based client of mine (really big) has a firewall making it impossible for iTunes to either grab album art, or get the radio stations list &#8212; even though that&#8217;s just regular http traffic.</p>
<p>Additionally, on the even of them launching their content being made available via iTunes, which was a big deal company wide, their firewall wouldn&#8217;t even allow the iTunes store connection &#8211; &#8220;not an approved application&#8221;. That was fun.</p>
<p>On the other hand, Apple has worked diligently with me a while back in order to make Quicktime streaming work through the same firewall (with an exception in the QT code, just to accommodate that particular case). </p>
<p>Oh yeah, and we&#8217;re also talking about MS based firewalls <img src='http://randommaccess.com/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /> </p>
<p>I don&#8217;t doubt that things have changed on Apple&#8217;s end, that would cause this problem you&#8217;re encountering, especially seeing as how Apple is pushing their reliance evangelical support of standards further with Leopard. One approach would be to work with your IT/network staff, though if they are MS-KoolAid drinkers, I see little hopes in any resolution from that end &#8211; though you may be surprised.</p>
<p>I&#8217;ll check a bit on my end, along with some of my Apple relations, and dig up if there&#8217;s any solution on the horizon, and let you know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck La Tournous</title>
		<link>http://randommaccess.com/2007/11/safari-youre-dead-to-me-now/comment-page-1/#comment-11</link>
		<dc:creator>Chuck La Tournous</dc:creator>
		<pubDate>Tue, 20 Nov 2007 15:31:26 +0000</pubDate>
		<guid isPermaLink="false">http://randommaccess.com/2007/11/19/safari-youre-dead-to-me-now/#comment-11</guid>
		<description>It&#039;s a pretty commonly know problem with ISA proxies, Harry -- the Apple Discussion Boards have a lot of threads on this going back to early Tiger revs (Here&#039;s a link to &lt;a href=&quot;http://discussions.apple.com/thread.jspa?messageID=5871394&quot; rel=&quot;nofollow&quot;&gt;one&lt;/a&gt;). The issue seems to be with the Windows 2003 Proxy Server -- MacWindows has a &lt;a href=&quot;http://www.macwindows.com/leopard.html#103107f&quot; rel=&quot;nofollow&quot;&gt;thread&lt;/a&gt; on it going back for the last couple of weeks. The fact that Mac OS 9 and Mac OS X 10.0 through 10.3 (as well as all versions of Windows) worked with this version of the proxy server indicates to me it&#039;s something that&#039;s changed in Apple&#039;s implementation. And I&#039;m not so much looking to place blame as to find a fix.

I didn&#039;t provide more details because I wasn&#039;t making a plea for help, just relating a situation -- but I do appreciate the offer.</description>
		<content:encoded><![CDATA[<p>It&#8217;s a pretty commonly know problem with ISA proxies, Harry &#8212; the Apple Discussion Boards have a lot of threads on this going back to early Tiger revs (Here&#8217;s a link to <a href="http://discussions.apple.com/thread.jspa?messageID=5871394" rel="nofollow">one</a>). The issue seems to be with the Windows 2003 Proxy Server &#8212; MacWindows has a <a href="http://www.macwindows.com/leopard.html#103107f" rel="nofollow">thread</a> on it going back for the last couple of weeks. The fact that Mac OS 9 and Mac OS X 10.0 through 10.3 (as well as all versions of Windows) worked with this version of the proxy server indicates to me it&#8217;s something that&#8217;s changed in Apple&#8217;s implementation. And I&#8217;m not so much looking to place blame as to find a fix.</p>
<p>I didn&#8217;t provide more details because I wasn&#8217;t making a plea for help, just relating a situation &#8212; but I do appreciate the offer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harry</title>
		<link>http://randommaccess.com/2007/11/safari-youre-dead-to-me-now/comment-page-1/#comment-10</link>
		<dc:creator>Harry</dc:creator>
		<pubDate>Tue, 20 Nov 2007 00:34:15 +0000</pubDate>
		<guid isPermaLink="false">http://randommaccess.com/2007/11/19/safari-youre-dead-to-me-now/#comment-10</guid>
		<description>Maybe if you gave some further details on the type of firewall you are facing, and what the issues are, you could be helpd - but blaming Safari/Apple for what is most likely an amateurish implementation of firewall (regardless of the size of your company) is disingenuous at best.

I count a major communications/entertainment company amongst my clients, and their firewall (or network) is pathetically configured, so I can sympathize with your plight. Again, though, blaming Apple for that misplaces the blame.

Provide some further information (or contact me via email) and we can try to troubleshoot this.</description>
		<content:encoded><![CDATA[<p>Maybe if you gave some further details on the type of firewall you are facing, and what the issues are, you could be helpd &#8211; but blaming Safari/Apple for what is most likely an amateurish implementation of firewall (regardless of the size of your company) is disingenuous at best.</p>
<p>I count a major communications/entertainment company amongst my clients, and their firewall (or network) is pathetically configured, so I can sympathize with your plight. Again, though, blaming Apple for that misplaces the blame.</p>
<p>Provide some further information (or contact me via email) and we can try to troubleshoot this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
