Quote:
Originally Posted by DiapDealer
OK, I'll try again:
In short, you've over-simplified what goes on between a web-server and the Kindle's browser. I repeat... it's not Amazon's problem. 
I may not be able to properly describe the problem (or the solution) in layman's terms, (and I realize that you have no reason to take my word for it) but I assure you... I know of which I speak. |
Thanks, with those clues I googled
[mime-type mobi content-type]
And got two threads here
https://www.mobileread.com/forums/showthread.php?t=99550
"You need to define the MIME type on your web server. Either of these should work for Kindle books:
application/x-mobipocket-ebook
application/octet-stream "
and the later
https://www.mobileread.com/forums/sho...d.php?t=106543
And also a Kindle 3 review which covered the topic
http://www.ebookworm.us/2011/01/03/m...le-by-kindles/
Is there any browser or other method of tracing to find out what the content headers being used are ?
I would say that if Kindle's browser won't accept application/octet-stream or
application/palm then there is a case that it's being too picky.
Thanks