![]() Now the magic: DC your device properly and restart, hit the sync button and watch magic happen ! I had to go back in the file and do a search & replace to make sure those urls did not use the HTTPS protocol and had the correct port appended. Now here comes the catch: I noticed as soon as I restarted my H2O it changed the image urls and multiple other endpoints to my api url. ![]() Its important to properly DC your device and remove it. ONLY remove and change the URL from the standard api.kobo store, and now you replace it with your updated API url. Kobo/Kobo and change the ereader conf file as following: I've had to remove the "https" protocol and change it to standard http, then add the port as :9696 (or whichever your install uses).Īpi_endpoint= Now go into your. Go to your calibre-web profile and create/view token, copy only the "url" and remove the https protocol and add your calibre port as following :Īpi_endpoint= Now here's the easy solution I've found to get working covers and sync and downloads on my H20 Libra. Quick heads up: I just rolled back from latest nightly to stable, see if that helps.Įnable Kobo sync and the feature to proxy unknown requests to kobostore if unknown (made no difference this on or off for me). The issue is not resolved by changing ports or not a biggie I use a reverse proxy to enter my own calibreweb install and now have got this to work as following: I've had the same problems as others: No covers, just metadata and cannot download the epub/pdf files (filetypes ARE supported). Wouldn't it just work out to add self.proxied=true to line 80 in reverseproxy.py to archive the same result?ĭear friends I have had been searching all the issues regarding Kobo sync, as I particularly bought a Kobo Libra H2O to sync with my wonderful calibre-web library. Now the problem in reverseproxy.py is that only proxies with path in it are detected, and not a port/host forward. So Calibre-web would be accessed from outside by and this is forwardes to. The docker is now "mapping" the internal port 8083 to an external port (let's say 80), I guess by some sort of reverse proxying. To work around this issue (which is a problem in non proxied applications, as all proxies I know would make a correct request out of it), the proxied case is detected in reverseproxy.py. The kobo reader has the "feature" to generate "abnormal" urls, if it sends a request on a non standard port like 8083, it will not include the port in the request string, so the kobo request would be: instead of the correct. If I get it right our problem is that calibre-web is generating wrong urls in the kobo section for downloads and other stuff, but any other links (like on page page, admin section and so on) are generated right. NET and web development experience who want to learn about API design.I'm not happy with the additional setting: Use code samples in API security implementationsĭevelopers and architects with. Review evolving APIs for monitoring and changing business requirements Implement API Gateways to streamline API DevelopmentĮxamine Security Mapping with API gateways from Azure and AWSĪpply API implementation using Serverless architecture This will prepare you for understanding the trade-off between security and the frictionless API experience. This book walks you through the API gateway services available in Azure and AWS and reviews different approaches to API Security. You'll then look at actual examples on API development guidelines, providing a practical view and approach towards the API development and aligning teams in API development. You'll decide on a sustainable API strategy and API architecture based on different case scenarios. This book starts off with an introduction to APIs and the concept of API Economy from a business and organizational perspective. Learn the business and technical importance of API design and architecture using the available cloud services from Azure and AWS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |