JOEBOX-L Archives

Joebox User

JOEBOX-L@LISTS.MAINE.EDU

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Kyle Green <[log in to unmask]>
Reply To:
Joebox User <[log in to unmask]>
Date:
Thu, 26 May 2011 15:50:00 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
I'm also seeing an issue where JoeBox RTF filtering breaks some
streaming services (like Netflix).

The first chunk loads fine, but subsequent chunks are blocked by the
RTF.  I've whitelisted the CDN for right now, but it'd be nice to know
why this is happening and if there's a way to adjust the RTF's
heuristics.

On May 26, 2011, at 3:31 PM, Ray Soucy <[log in to unmask]> wrote:

> All,
>
> We have found an issue with some CDN (Content Delivery Network)
> provides when X-Forwarded-For headers are included (as is done with
> most proxy servers, including Bess) for private (RFC 1918) IP
> addresses.  The CDNs in question would see the RFC 1918 address and
> default to directing traffic to data-centers that are often not the
> closest or fastest for content.
>
> This may have made browsing some websites seem slow for those using
> private addressing.
>
> We are currently testing an update from MECnet to resolve this and
> will be posting it on the update server shortly.
>
> This update will appear as mecguard_maine 12.3
>
> --
> Ray Soucy
>
> Epic Communications Specialist
>
> Phone: +1 (207) 561-3526
>
> Networkmaine, a Unit of the University of Maine System
> http://www.networkmaine.net/

ATOM RSS1 RSS2