Page 2 of 2

Re: 2010-07-13 outage *RESOLVED*

PostPosted: Wed Jul 14, 2010 2:41 pm
by Glenn1963
Continuing with the hijack, WiRNS is also getting the "(505) Http Version Not Supported" error.

As a WiRNS developer, any debugging assistance or other information is available if required.

Thanks!

-Glenn R

Re: 2010-07-13 outage *RESOLVED*

PostPosted: Wed Jul 14, 2010 8:33 pm
by Glenn1963
Further to the "505: HTTP Version Not Supported" errors, the problem seems to occur if you try HTTP 1.1 requests. Forcing HTTP 1.0 seems to solve the problem.

-G

Re: 2010-07-13 outage *RESOLVED*

PostPosted: Tue Jul 20, 2010 9:08 pm
by mbluett
The outage is not resolved from my perspective: I am still receiving Http Version Not Supported using the latest version of GBPVR. I have tried many times to get an update, but it continues to fail.

Is there a way that I can download the schedule manually (i.e., via FTP of SFTP) ? If so, where on the Schedulesdirect.org site to I do this ?

Re: 2010-07-13 outage *RESOLVED*

PostPosted: Tue Jul 20, 2010 11:11 pm
by rmeden
The outage referred to the SD web site being down, and *nothing* worked.

Progress is being made on the 505 error.

In the mean time, the easiest way to download data is with XMLTV/tv_grab_na_dd.

You can also use sample code in the developer section of this forum.

Robert

Re: 2010-07-13 outage *RESOLVED*

PostPosted: Wed Jul 21, 2010 9:44 am
by mbluett
I have a compiled application of which I do not have the source code and therefore cannot change the HTTP version it is using. And even if I could the server should be able to handle v1.1 .

So until there is a resolution, can I download the data in another way and then make it available to GBPVR ?

Re: 2010-07-13 outage *RESOLVED*

PostPosted: Wed Jul 21, 2010 10:32 am
by rmeden
Yes, GBPVR can import a file generated by XMLTV/tv_grab_na_dd.

But it's a moot point... the 505 problem was just fixed. See if you can download now.

Robert

Re: 2010-07-13 outage *RESOLVED*

PostPosted: Wed Jul 21, 2010 2:40 pm
by mbluett
Yes, thank you. The problem is indeed resolved.