HTMLDocumentProtector returns token once generated
This library doesn't get many releases because of it's simplicity, but today we're releasing a simple change as an improvement that WebEngine will take advantage of straight away.
The protectAndInject
function of the HTMLDocumentProtector now returns the token it generates, which will be used to send the token as a response header in the WebEngine's dispatcher.
The purpose of this change is simply to make client-side development slightly easier when dealing with CSRF tokens, specifically when making POST requests, such as when uploading a file using the browser's fetch API.