mod_websocket: Fire pre-session-close event (fixes #1800) This event was added in a7c183bb4e64 and is required to make mod_smacks know that a session was intentionally closed and shouldn't be hibernated (see fcea4d9e7502). Because this was missing from mod_websocket's session.close(), mod_smacks would always attempt to hibernate websocket sessions even if they closed cleanly. That mod_websocket has its own copy of session.close() is something to fix another day (probably not in the stable branch). So for now this commit makes the minimal change to get things working again. Thanks to Damian and the Jitsi team for reporting.

     1

local data_path = "../../data";

     2

     3

local vhost = {

     4

	"accounts",

     5

	"account_details",

     6

	"roster",

     7

	"vcard",

     8

	"private",

     9

	"blocklist",

    10

	"privacy",

    11

	"archive-archive",

    12

	"offline-archive",

    13

	"pubsub_nodes-pubsub",

    14

	"pep-pubsub",

    15

}

    16

local muc = {

    17

	"persistent",

    18

	"config",

    19

	"state",

    20

	"muc_log-archive",

    21

};

    22

    23

input {

    24

	hosts = {

    25

		["example.com"] = vhost;

    26

		["conference.example.com"] = muc;

    27

	};

    28

	type = "internal";

    29

	path = data_path;

    30

}

    31

    32

output {

    33

	type = "sql";

    34

	driver = "SQLite3";

    35

	database = data_path.."/prosody.sqlite";

    36

}

    37

    38

--[[

    39

    40

input {

    41

	type = "internal";

    42

	path = data_path;

    43

}

    44

output {

    45

	type = "sql";

    46

	driver = "SQLite3";

    47

	database = data_path.."/prosody.sqlite";

    48

}

    49

    50

]]