Empty X-Bunq-Client-Authentication headers result in HTTP 403 forbidden errors

[holtkamp]

Currently an 'empty' X-Bunq-Client-Authentication header is used in some initial request (like POST Installation), which results in a HTTP 403 forbidden error since 27-03-2018.

bunq/src/Middleware/RequestIdMiddleware.php

Lines 37 to 39 in c48f3d1

	if (!isset($headers['X-Bunq-Client-Authentication'])) {
	$headers['X-Bunq-Client-Authentication'] = $this->sessionToken;
	}

It should only be set when required:

        if (\is_string($this->sessionToken) && $this->sessionToken !== '' && !isset($headers['X-Bunq-Client-Authentication'])) {
            $headers['X-Bunq-Client-Authentication'] = $this->sessionToken;
        }

Would a PR be accepted? Or is none of the maintainers monitoring this?