BOSH over HTTPS in Chrome

I was wondering if anybody else had problems using BOSH over HTTPS in Chrome?

Here is my listeners configuration from ejabberd.cfg:

%%% ===============
%%% LISTENING PORTS

%%
%% listen: Which ports will ejabberd listen, which service handles it
%% and what options to start it with.
%%
{listen,
[

{5222, ejabberd_c2s, [
{certfile, "/opt/ejabberd-2.1.10/conf/server.pem"}, starttls,
{access, c2s},
{shaper, c2s_shaper},
{max_stanza_size, 65536}
]},

%%
%% To enable the old SSL connection method in port 5223:
%%
%%{5223, ejabberd_c2s, [
%% {certfile, "/opt/ejabberd-2.1.10/conf/server.pem"}, tls,
%% {access, c2s},
%% {shaper, c2s_shaper},
%% {max_stanza_size, 65536}
%% ]},

{5269, ejabberd_s2s_in, [
{shaper, s2s_shaper},
{max_stanza_size, 131072}
]},

%%
%% ejabberd_service: Interact with external components (transports...)
%%
%%{8888, ejabberd_service, [
%% {access, all},
%% {shaper_rule, fast},
%% {ip, {127, 0, 0, 1}},
%% {hosts, ["icq.example.org", "sms.example.org"],
%% [{password, "secret"}]
%% }
%% ]},

{5280, ejabberd_http, [
%%{request_handlers, [
%% {["web"], mod_http_fileserver}
%%]},
captcha,
http_poll,
web_admin
]},

{8092, ejabberd_http, [
http_bind
]},

{443, ejabberd_http, [
http_bind,
tls, {certfile, "/opt/ejabberd-2.1.10/conf/server.pem"}
]}

]}.

Note that I am using port 8092 for HTTP, and port 443 for HTTPS using the default certificate which is shipped with ejabberd.

I can connect to http://mydomain.com:8092/http-bind fine in both Firefox and Chrome.

I was able to connect to https://mydomain.com/http-bind in Firefox after being asked to accept the untrustworthy certificate.

However, in Chrome, the connection simply hangs when trying to access the HTTPS URL. Using netstat on the ejabberd node shows that a connection has been established on port 443.

Has anybody else experienced HTTPS problems in Chrome? The fact that I can connect in Firefox suggests it is a Chrome-specific problem with HTTPS....