Something on your mind? Want to give us feedback on something in particular or everything in general? Tell us how we are doing!
#11485 by ggilman
Sun Jun 14, 2009 7:03 pm
It's broke in my Chrome.

It works fine in my Firefox, IE, and Safari though. Yes, I actually use all of these regularly, not just for testing. :?
#11505 by Bobby B
Mon Jun 15, 2009 9:57 am
Yep, breaks in my chrome -- We've filed an internal bug to get this one fixed.
#12422 by dmlanger
Wed Jul 01, 2009 10:49 am
Just wondering if this has been fixed. It doesnt appear so to me. It's a very simple fix adding 6 characters to the beginning of the documents <html>, so i dont know why it could not be fixed.
#12469 by koehn
Thu Jul 02, 2009 7:43 am
This bug is also the reason people cannot access using a proxy.
#12477 by dmlanger
Thu Jul 02, 2009 9:51 am
koehn wrote:This bug is also the reason people cannot access using a proxy.

No its not. The reason it cant be accessed is because runs locally on your ooma hub. if you go through a proxy you wont be able to access it because you will be outside of your network.
#12766 by koehn
Wed Jul 08, 2009 11:06 am
Not necessarily true, and certainly not in my case, where my proxy server is inside my LAN, behind the Ooma.

I get the parent frame of, but the subframe that takes up the majority of the page gets an error from the proxy server.
#12769 by dmlanger
Wed Jul 08, 2009 11:39 am
Oh ok. It could be that your proxy server does not fetch pages that dont start with an <html> tag. What browser have u tried this in?

Who is online

Users browsing this forum: No registered users and 8 guests