I'm using JSJaC 1.2 with today's trunk ejabberd + http_bind. Compiled on OTP R11B5.
I have http_bind working without TLS, but when I try to enable TLS, as so:
{5280, ejabberd_http, [
tls, {certfile, "/home/bjc/etc/ssl/host.pem"},
{request_handlers, [{["views"], mod_http_fileserver},
{["http-bind"], mod_http_bind}]},
http_poll,
web_admin
]}I can no longer use the http-bind interface. It's worth noting that I can still log in via web_admin and TLS.
Eventually, I get the following on the ejabberd console:
=CRASH REPORT==== 18-Jan-2008::22:38:25 ===
crasher:
pid: <0.396.0>
registered_name: []
error_info: {function_clause,[{ejabberd_http,get_line,[[],[]]},
{ejabberd_http,get_headers,2},
{ejabberd_http,parse_request,2},
{ejabberd_http,receive_headers,1},
{proc_lib,init_p,5}]}
initial_call: {ejabberd_http,
receive_headers,
[{state,
tls,
{tlssock,#Port<0.482>,#Port<0.483>},
undefined,
undefined,
undefined,
undefined,
undefined,
undefined,
"en",
[{["views"],mod_http_fileserver},
{["http-bind"],mod_http_bind},
{["admin"],ejabberd_web_admin},
{["http-poll"],ejabberd_http_poll}],
false,
[]}]}
ancestors: [ejabberd_http_sup,ejabberd_sup,<0.39.0>]
messages: []
links: [<0.261.0>,#Port<0.482>]
dictionary: []
trap_exit: false
status: running
heap_size: 1597
stack_size: 21
reductions: 4705
neighbours:
=SUPERVISOR REPORT==== 18-Jan-2008::22:38:25 ===
Supervisor: {local,ejabberd_http_sup}
Context: child_terminated
Reason: {function_clause,[{ejabberd_http,get_line,[[],[]]},
{ejabberd_http,get_headers,2},
{ejabberd_http,parse_request,2},
{ejabberd_http,receive_headers,1},
{proc_lib,init_p,5}]}
Offender: [{pid,<0.396.0>},
{name,undefined},
{mfa,
{ejabberd_http,
start_link,
[{gen_tcp,#Port<0.482>},
[tls,
{certfile,"/home/bjc/etc/ssl/host.pem"},
{request_handlers,
[{["views"],mod_http_fileserver},
{["http-bind"],mod_http_bind}]},
http_poll,
web_admin]]}},
{restart_type,temporary},
{shutdown,brutal_kill},
{child_type,worker}]
Can anyone offer any advice?
I get exactly the same
I get exactly the same result. I wrote a report here:
I've encountered similar
I've encountered similar problems but bug can be different more information in bugtrack: