additionalHeaders and rejectUnauthorized are not respected by the extension

[rozpuszczalny]

Both additionalHeaders and rejectUnauthorized options are not respected by the extension.

Steps to reproduce:

1. Set redmine.additionalHeaders to {"Authorization": "Anything"}
2. Set redmine.url to any webserver address, which can intercept headers (e.g. Burp Suite)
3. Run Redmine: List open issues assigned to me

Expected results

Request headers should include Authorization: Anything.

Actual results

No header Authorization is found in the request headers.

Note for new-commers

Creating new instance of RedmineServer does not include additionalHeaders and rejectUnauthorized from configuration. One needs to additionally parse and pass these options into the new instances. These are created in src/extension.ts, src/trees/my-issues-tree.ts and src/trees/projects-tree.ts:

vscode-redmine/src/trees/projects-tree.ts

Lines 11 to 18 in cbf738d

	const config = vscode.workspace.getConfiguration(
	"redmine"
	) as RedmineConfig;
	this.server = new RedmineServer({
	address: config.url,
	key: config.apiKey,
	});
	}

vscode-redmine/src/trees/my-issues-tree.ts

Lines 9 to 15 in cbf738d

	const config = vscode.workspace.getConfiguration(
	"redmine"
	) as RedmineConfig;
	this.server = new RedmineServer({
	address: config.url,
	key: config.apiKey,
	});

vscode-redmine/src/extension.ts

Lines 57 to 64 in cbf738d

	const config = vscode.workspace.getConfiguration(
	"redmine",
	v && v.uri
	) as RedmineConfig;
	const redmineServer = new RedmineServer({
	address: config.url,
	key: config.apiKey,
	});

Thanks to @saiballo for spotting that!

[saiballo]

any news about this issue? :-)

[rozpuszczalny]

@saiballo I was hoping that some newcomer will pick the issue and solve it ;) Anyway, since no one is interested in it, I'll fix it soon then

[saiballo]

thank you very much!!!