File

util.jwt: Add support/tests for ES256 via improved API and using util.crypto In many cases code will be either signing or verifying. With asymmetric algorithms it's clearer and more efficient to just state that once, instead of passing keys (and possibly other parameters) with every sign/verify call. This also allows earlier validation of the key used. The previous (HS256-only) sign/verify methods continue to be exposed for backwards-compatibility.

local record serve_options
	path : string
	mime_map : { string : string }
	cache_size : integer
	cache_max_file_size : integer
	index_files : { string }
	directory_index : boolean
end

local record http_files
	serve : function(serve_options|string) : function
end

return http_files