incubator-wave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ali Lown <>
Subject Re: Problem with WIAB SSL enabled an Chrome/Chromium
Date Tue, 19 Feb 2013 12:37:47 GMT
It is possible that it is related to the timeout issues when you attempt to
access SSL secured wave from the Chrome Android client. (I traced this to
an issue with Chrome for Android and/or Jetty, but never fully resolved it.)

It is also possible that this is related to the fact that you are using a
self-signed cert and GAE is set to reject connection attempts to non-valid
certificates. [0, 1]

So, could you try using a valid CA certificate (e.g. from StartSSL (ensure
you also import the intermediate certificate or it will still be considered
You could instead try disable the certificate validation as documented in

If this doesn't solve it, then it is probably a problem with the NIO
handling in the version of Jetty we are using.


On 19 Feb 2013 12:13, "Niklaus Hofer" <> wrote:

> On 02/19/2013 12:44 PM, Ali Lown wrote:
> >> > I changed the source so all urls say "https" instead of "http". But
> >> > Any idea what the cause of that is and/or how I can fix it?
> > Just to check: with SSL disabled, and prior to changing the Microbox
> > code, did the DataApiOAuth work?
> I had to reconfigure my sever to not use SSL. Then reverted my
> changes to microbox and deployed it. Now it works fine w/o SSL.
> > I am trying to determine whether this is a SSL specific issue or a
> DataApi issue
> So the problem appears to be SSL specific.
> --
> Freundliche Gruesse
> Niklaus Manuel Hofer
> ()  ascii ribbon campaign - against html e-mail
> /\   - against proprietary attachments

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message