Probable solution to '505: HTTP Version Not Supported'

Forum rules
Get Help using the Schedules Direct service. NOTE: application issues are probably better resolved via the application's support methods. If you post here, at least include your application name!
rmeden
SD Board Member
Posts: 1529
Joined: Tue Aug 14, 2007 2:31 pm
Location: Cedar Hill, TX
Contact:

Re: Probable solution to '505: HTTP Version Not Supported'

Post by rmeden »

I just got off a conference call with Tribune and they have just rolled the 505 fix to the production servers.

Thanks to all the folks who helped troubleshoot this.

I'll be updating the open issues thread with the other issues.

viewtopic.php?f=3&t=931

Robert

barzon
Posts: 2
Joined: Wed Jul 21, 2010 11:32 am

Re: Probable solution to '505: HTTP Version Not Supported'

Post by barzon »

Not fixed here on 2 computers, still receiving a 505 error

Glenn1963
Posts: 7
Joined: Wed Jul 14, 2010 2:36 pm

Re: Probable solution to '505: HTTP Version Not Supported'

Post by Glenn1963 »

I agree, still getting 505 on production servers.

rmeden
SD Board Member
Posts: 1529
Joined: Tue Aug 14, 2007 2:31 pm
Location: Cedar Hill, TX
Contact:

Re: Probable solution to '505: HTTP Version Not Supported'

Post by rmeden »

darn!... just sent them an email.

rmeden
SD Board Member
Posts: 1529
Joined: Tue Aug 14, 2007 2:31 pm
Location: Cedar Hill, TX
Contact:

Re: Probable solution to '505: HTTP Version Not Supported'

Post by rmeden »

Ok... I need more help troubleshooting this.

If you are still experiencing the 505 problem (Yes, Glen, this means you. :) ) can you please send me an email at admin/schedulesdirect.org with the following:

1. Application you are using.
2. OS You're using
3. If the application uses .NET (if you know)
4. Wireshark or tcpdump capture of a failed grab.

Thanks

Robert

rmeden
SD Board Member
Posts: 1529
Joined: Tue Aug 14, 2007 2:31 pm
Location: Cedar Hill, TX
Contact:

Re: Probable solution to '505: HTTP Version Not Supported'

Post by rmeden »

I just reviewed two CW_EPG sniffer traces.

Both were not getting a "505 HTTP Version not supported", they were getting "400 HTTP Method GET is not supported by this URL".

The request was a HTTP HEAD message. I think the TMS 400 response is correct. I know I would sometimes query the TMS server with a browser (HTTP GET) and look for a "HTTP Method GET not supported" error as a sign of success.

I don't see how CW_EPG has ever worked, but it's certainly not the 505 problem.

I'm participating in their forum to try and resolve this. A code change may be needed on the CW_EPG side.

Still waiting for proof of a 505 issue.

Robert

barzon
Posts: 2
Joined: Wed Jul 21, 2010 11:32 am

Re: Probable solution to '505: HTTP Version Not Supported'

Post by barzon »

working now Thank You

reverson1
Posts: 3
Joined: Tue Jul 20, 2010 8:41 am

Re: Probable solution to '505: HTTP Version Not Supported'

Post by reverson1 »

I don't understand why mc2xml worked yesterday and for the record didn't, but 4tr is working today.

Glenn1963
Posts: 7
Joined: Wed Jul 14, 2010 2:36 pm

Re: Probable solution to '505: HTTP Version Not Supported'

Post by Glenn1963 »

Working now with WiRNS as well, thanks Robert.

-G

Post Reply