On Tue, Oct 6, 2020 at 4:53 PM Sam Ruby wrote:
>
> When the client
> connected to the websocket process directly it made a lot of sense for
> that process to implement SSL. Now that that is no longer the case,
> it no longer is necessary. In fact, it no longer is necessary for the
> websocket to
On Sat, Oct 24, 2020 at 7:00 PM sebb wrote:
>
> On Sat, 24 Oct 2020 at 19:40, wrote:
> >
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > rubys pushed a commit to branch master
> > in repository https://gitbox.apache.org/repos/asf/whimsy.git
> >
> >
> > The followin
On Sat, 24 Oct 2020 at 19:40, wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> rubys pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/whimsy.git
>
>
> The following commit(s) were added to refs/heads/master by this push:
>
I made some improvements to the websocket client test tool, and ran
some tests on whimsy-vm6. Based on the results below, it appears that:
1) The websocket service process is operating correctly on whimsy-vm6
2) The Apache httpd ssl proxy is hanging on whimsy-vm6
3) Both the service process and
