Allow csrf to be updated on cookie refresh and add 401 error handling #148
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
if (!this.csrf && ar && ar.length >= 2) {
prevents the csrf being updated after a re-init with former registration data has returned a new csrf, this will result in 401 errors on certain commands (such as speech) if the csrf is out of date.
Also this doesnt appear to do anything:
if (!ar || ar.length < 2) ar = this.cookie.match(/csrf=([^;]+)/);
Also added handling of 401 errors (otherwise the failure is silent)
Should fix:
#57
fixes bbindreiter/node-red-contrib-alexa-remote2-applestrudel#2
fixes cakebake/node-red-contrib-alexa-remote-cakebaked#31