MobileRead Forums - View Single Post - Calibre Content Server d/l fails on Android

Mogrith · 09-20-2010, 07:55 PM

If I log into server with a Windows browser I can d/l books with no problems.

But on android browsers It always fails.

Has anyone d/l a book from the content server to an android device?

Tried asking on the Calibre forum but no luck.
log looks like this

192.168.1.5 - mogrith [18/Sep/2010:15:20:39] "GET /get/EPUB/Bull, Emma|Bear, Elizabeth|Monette, Sarah|Shetterly, Will|Downum, Amanda|Shipman, Stephan-Shadow Unit - Season 1_9407.EPUB HTTP/1.1" 200 1061457 "http://192.168.1.2:8080/mobile?num=25&search=epub&sort=date&order=descendi ng" "Mozilla/5.0 (Linux; U; Android 2.1-update1; en-us; Android for Telechips TCC8900 Evaluation Board (US) Build/ECLAIR) AppleWebKit/530.17 (KHTML, like Gecko) Version/4.0 Mobile Safari/530.17"
192.168.1.5 - - [18/Sep/2010:15:21:25] "GET /get/EPUB/Bull, Emma|Bear, Elizabeth|Monette, Sarah|Shetterly, Will|Downum, Amanda|Shipman, Stephan-Shadow Unit - Season 1_9407.EPUB HTTP/1.1" 401 1109 "" "Mozilla/5.0 (Linux; U; Android 2.1-update1; en-us; Android for Telechips TCC8900 Evaluation Board (US) Build/ECLAIR) AppleWebKit/530.17 (KHTML, like Gecko) Version/4.0 Mobile Safari/530.17

It looks like I'm getting 401 errors.
10.4.2 401 Unauthorized

The request requires user authentication. The response MUST include a
WWW-Authenticate header field (section 14.47) containing a challenge
applicable to the requested resource. The client MAY repeat the
request with a suitable Authorization header field (section 14.8). If
the request already included Authorization credentials, then the 401
response indicates that authorization has been refused for those
credentials. If the 401 response contains the same challenge as the
prior response, and the user agent has already attempted
authentication at least once, then the user SHOULD be presented the
entity that was given in the response, since that entity might
include relevant diagnostic information. HTTP access authentication
is explained in "HTTP Authentication: Basic and Digest Access
Authentication" [43].

09-20-2010, 07:55 PM	#1
Mogrith Member Posts: 10 Karma: 10 Join Date: May 2008 Location: Brea, CA Device: K1,K2, Broken 505,M003(android 1.6)	Calibre Content Server d/l fails on Android If I log into server with a Windows browser I can d/l books with no problems. But on android browsers It always fails. Has anyone d/l a book from the content server to an android device? Tried asking on the Calibre forum but no luck. log looks like this 192.168.1.5 - mogrith [18/Sep/2010:15:20:39] "GET /get/EPUB/Bull, Emma\|Bear, Elizabeth\|Monette, Sarah\|Shetterly, Will\|Downum, Amanda\|Shipman, Stephan-Shadow Unit - Season 1_9407.EPUB HTTP/1.1" 200 1061457 "http://192.168.1.2:8080/mobile?num=25&search=epub&sort=date&order=descendi ng" "Mozilla/5.0 (Linux; U; Android 2.1-update1; en-us; Android for Telechips TCC8900 Evaluation Board (US) Build/ECLAIR) AppleWebKit/530.17 (KHTML, like Gecko) Version/4.0 Mobile Safari/530.17" 192.168.1.5 - - [18/Sep/2010:15:21:25] "GET /get/EPUB/Bull, Emma\|Bear, Elizabeth\|Monette, Sarah\|Shetterly, Will\|Downum, Amanda\|Shipman, Stephan-Shadow Unit - Season 1_9407.EPUB HTTP/1.1" 401 1109 "" "Mozilla/5.0 (Linux; U; Android 2.1-update1; en-us; Android for Telechips TCC8900 Evaluation Board (US) Build/ECLAIR) AppleWebKit/530.17 (KHTML, like Gecko) Version/4.0 Mobile Safari/530.17 It looks like I'm getting 401 errors. 10.4.2 401 Unauthorized The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field (section 14.8). If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity might include relevant diagnostic information. HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" [43].