mod_http: Allow disabling CORS in the http_cors_override option and by default Fixes #1779. Due to an oversight in the logic, if the user set 'enabled' to false in an override, it would disable the item's requested CORS settings, but still apply Prosody's default CORS policy. This change ensures that 'enabled = false' will now disable CORS entirely for the requested item. Due to the new structure of the code, it was necessary to have a flag to say whether CORS is to be applied at all. Rather than hard-coding 'true' here, I chose to add a new option: 'http_default_cors_enabled'. This is a boolean that allows the operator to disable Prosody's default CORS policy entirely (the one that is used when a module or config does not override it). This makes it easier to disable CORS and then selectively enable it only on services you want it on.

     1

-- Prosody IM

     2

-- Copyright (C) 2008-2010 Matthew Wild

     3

-- Copyright (C) 2008-2010 Waqas Hussain

     4

--

     5

-- This project is MIT/X11 licensed. Please see the

     6

-- COPYING file in the source package for more information.

     7

--

     8

     9

    10

    11

local unpack = table.unpack or unpack; --luacheck: ignore 113

    12

local t_insert = table.insert;

    13

function _G.import(module, ...)

    14

	local m = package.loaded[module] or require(module);

    15

	if type(m) == "table" and ... then

    16

		local ret = {};

    17

		for _, f in ipairs{...} do

    18

			t_insert(ret, m[f]);

    19

		end

    20

		return unpack(ret);

    21

	end

    22

	return m;

    23

end