Great questions. I've responded inline below:
On Friday, March 25, 2016 at 6:52:09 AM UTC-5, Matthew Wild wrote:
>
> Hi Aaron,
> [snip]
>
> Just to confirm, are you saying 0.10 build 181 works, and 182 does
> not? (for the record, that seems unlikely) or is the exact build that
> breaks unkno
Hi Aaron,
On 22 March 2016 at 21:46, Aaron van Meerten wrote:
> Hi Prosody People,
>
> I have prosody set up for bosh, and am forwarding requests to /http-bind in
> nginx to prosody on 5280. When using this configuration with
> prosody-0.10-nightly181, I have had no issues running the service.
>
Hi Prosody People,
I have prosody set up for bosh, and am forwarding requests to /http-bind in
nginx to prosody on 5280. When using this configuration with
prosody-0.10-nightly181, I have had no issues running the service.
However, now I have been experiencing this strange issue on all builds
