What would cause a BOSH response like the following:
<body type='terminate' condition='undefined-condition' xmlns='http://jabber.org/protocol/httpbind'>Request Too Large</body>This happens when the total POST body gets above about 66k. From the ejabberd log file, I see the following log messages right around the time this happens, exactly after the with the very large message is printed to the log (changed the jabberd id to protect the innocent):
=INFO REPORT==== 2011-02-14 19:33:40 ===
D(<0.3936.0>:ejabberd_http_bind:549) : terminate: Deleting session 430ad777c6a086c36e179cc9e7c11f52125de4e8
=INFO REPORT==== 2011-02-14 19:33:40 ===
I(<0.3937.0>:ejabberd_c2s:1409) : ({socket_state,ejabberd_http_bind,{http_bind,<0.3936.0>,{{10,2,9,12},56151}},ejabberd_http_bind}) Close session for xxx@yyy.com/zzz
Is there a setting that can be changed in the ejabberd.cfg file to avoid this issue? Already tried changing the c2s shaper, but it did not seem to make a difference. Also tried looking at line 549 of ejabberd_http_bind.erl, but can't figure out what's going on. Also could not find the string "condition='undefined-condition'" anywhere in the source.
Any help would be greatly appreciated.
ryanhope wrote: <body
<body type='terminate' condition='undefined-condition' xmlns='http://jabber.org/protocol/httpbind'>Request Too Large</body>This happens when the total POST body gets above about 66k.
Is there a setting that can be changed in the ejabberd.cfg file to avoid this issue?
{max_stanza_size, 65536}
Is a max stanza size of 1 MB
Is a max stanza size of 1 MB (e.g. {max_stanze_size, 1048576} ) an unreasonable value as far as ejabberd is concerned? What's a reasonable upper limit for max_stanza_size?