Thread: Replacing Kobo Bookstore
View Single Post
Old 03-28-2017, 08:20 PM   #62
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by kido.resuri View Post
The authorization header is x-kobo-userkey and the header value is your ClientId, which can be found in .kobo/Kobo/Analytics.cong
Are you sure of that? It doesn't match the value used here. And the database would be a better source.
Quote:
If you add these custom headers, the kobo servers will start responding. The Kobo eReader requests all data in json format, by using the headers "Accept" - "application/json" and "Accept-Encoding" - "gzip" and "Content-Type" - "application/json". Some data uses "text/json", so every packet must be analyzed one by one.
I also changed the "User-Agent" header to
Code:
"Mozilla/5.0 (Linux; U; Android 2.0; en-us;) AppleWebKit/538.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/538.1 (Kobo Touch)"
as this is what Kobo eReader use.
From an experiment I did ages ago, the server doesn't check the user agent.
davidfor is offline   Reply With Quote