View Single Post
Old 05-14-2014, 01:31 AM   #1006
Rev. Bob
Wizard
Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.
 
Rev. Bob's Avatar
 
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
Quote:
Originally Posted by davidfor View Post
My workaround, which I don't like is to put the userid and password in the URL. Such as:

Code:
http://userid:password@127.0.0.1:80
That works, while exposing another shortcoming of the browser: it rejects some addresses without even trying them.

My particular use case is a Sandisk Wireless Flash Drive, which can connect to a larger wifi network and make itself visible as http://sandisknnnnnn.local/files/ - where the bolded part is derived from the unit's MAC address.

With my iPad, I can access that URL directly, either with or without the hack you describe. With the Kobo, I can only access it through the IP address and with the hack. The only thing I can think of to explain that is that the Kobo is looking at the ".local" and saying "I know that's not real" instead of actually checking.
Rev. Bob is offline   Reply With Quote