W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2011

[Bug 14310] Make responseheaders visible on <video> and <audio> element

From: <bugzilla@jessica.w3.org>
Date: Sun, 02 Oct 2011 21:05:05 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RATDd-0003oB-Ve@jessica.w3.org>

--- Comment #3 from Offbeatmammal <offbeatmammal@gmail.com> 2011-10-02 21:05:05 UTC ---
some CDNs with multiple PoPs (points of presence, nodes or other similar term)
can add additional header information to indicate which pop/nodes was actually
used to deliver content to the user

for instance... the origin for the video file may be in your data center but
you distribute it via a CDN with nodes in San Fran, Columbus ,Atlanta, Denver,
NYC, and London... and they logic should determine which pop delivers content
to a consumer in LA, Detroit or Bonn. For tracking/debug the CDN injects some
additional information (either as a header or a cookie) to indicate which POP
it was served from / where the user has affinity for the current session.

In some scenarios a POP may be having an issue, it may have bad content (old or
corrupt) cached or it may simply be that for network logic reasons it's not the
right node to affiliate a particular user to ... by allowing the requesting
client to access that information (something we do have in Flash, Silverlight
etc) and report it back to a QA system it's possible to carry out the same
level of debugging or reporting

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 2 October 2011 21:05:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:05 UTC