[mythtv-users] webservices.schedulesdirect.tmsdatadirect.com -- 401 unauthorized

Marc Randolph mrand at pobox.com
Thu Jan 15 22:17:57 UTC 2009


On Thu, Jan 15, 2009 at 3:38 PM, Michael T. Dean
<mtdean at thirdcontact.com> wrote:
> On 01/15/2009 04:09 PM, Brad DerManouelian wrote:
>> On Jan 15, 2009, at 1:01 PM, Igor Chudov wrote:
>>
>>> I registered for a 7 day of Schedules Direct trial yesterday, hoping
>>> to test this service out before paying to use it.
>>>
>>> I use MythTV on Ubuntu Intrepid.
>>>
>>> When running mythfilldatabase, I get a lot of errors such as this one:
>>>
>>> 2009-01-15 14:49:44.715 Grabbing listing data
>>> --2009-01-15 14:49:44-- http://webservices.schedulesdirect.tmsd
>>> ... tvdService
>>> Resolving
>>> webservices.schedulesdirect.tmsdatadirect.com... 206.18.98.175
>>> Connecting to
>>> webservices.schedulesdirect.tmsdatadirect.com|206.18.98.175|:80...
>>> connected.
>>> HTTP request sent, awaiting response... 401 Unauthorized
>>> Reusing existing connection to
>>> webservices.schedulesdirect.tmsdatadirect.com:80.
>>> HTTP request sent, awaiting response... 401 Unauthorized
>>> Authorization failed.
>>> 2009-01-15 14:49:44.972 Grab complete. Actual data from to (UTC)
>>>
>> This is supposed to happen. You're getting redirected to a "please
>> sign in" type of page after your initial attempt fails. Then a second
>> attempt is made and it works.
>
> Shouldn't it be only one 401 followed by a 200?  I.e. the first 401 is
> the request for credentials, then when good credentials are passed, we
> get an OK response status.

Yes.... there is a "200 OK" following the 401:

Resolving webservices.schedulesdirect.tmsdatadirect.com... 206.18.98.175
Connecting to webservices.schedulesdirect.tmsdatadirect.com|206.18.98.175|:80...
connected.
HTTP request sent, awaiting response... 401 Unauthorized
Reusing existing connection to webservices.schedulesdirect.tmsdatadirect.com:80.
HTTP request sent, awaiting response... 200 OK


   Marc


More information about the mythtv-users mailing list