Hi Chris,

There are changes underway with the TPEG feeds but so far as we are
aware there's no specific management of access from individual IPs, at
least not intentionally.  I've passed your enquiry to the migration team
and they should have a little more information soon.  The overall
availability will be reduced in the coming days,

Ant 

-----Original Message-----
From: owner-backst...@lists.bbc.co.uk
[mailto:owner-backst...@lists.bbc.co.uk] On Behalf Of Chris Northwood
Sent: 08 March 2011 12:44
To: backstage@lists.bbc.co.uk
Subject: [backstage] BBC TPEG feeds - oddities?

Hi there,

So, I'm a bit confused at the moment with the state of the TPEG travel
news feeds that are being provided by the BBC. I notice there's been
some changes, but I'm not sure exactly what.

I'm also seeing some very odd behaviour from the BBC site depending on
what IP I access the feed from.

>From my PC: I run:

wget http://www.bbc.co.uk/travelnews/tpeg/en/local/rtm/oxford_tpeg.xml

and get what looks like what I want, an XML document with up-to-date
travel alerts in

2011-03-08 12:33:40 (2.24 MB/s) - `oxford_tpeg.xml' saved [30469/30469]

However, on the webserver, SSH'd in, I run exactly the same wget
command:

and get a considerably shorter file back:

2011-03-08 12:26:16 (216 MB/s) - `oxford_tpeg.xml' saved [1798/1798]

Which contains only the "From 6 March 2011, we will be discontinuing
access"... message

So, I'm completely foxed with what's going on here - has our webserver
been blacklisted from the TPEG feeds or something? :S

Regards,

Chris Northwood,
Web Developer (Mobile Oxford)
-
Sent via the backstage.bbc.co.uk discussion group.  To unsubscribe,
please visit
http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
Unofficial list archive:
http://www.mail-archive.com/backstage@lists.bbc.co.uk/

-
Sent via the backstage.bbc.co.uk discussion group.  To unsubscribe, please 
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.  
Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/

Reply via email to