fix: Workaround csrf redirects

[marikaner]

Context

The issue behind csrf requests not working on On-Premise systems is a bug in axios (axios/axios#3369). The http proxy agent config is missing in the second request, when there is a redirect. I added a workaround to achieve the correct redirect behavior. This issue was opened by a user here: #617

Definition of Done

Please consider all items and remove only if not applicable.

• Tests created/adjusted for your changes.
• Release notes updated.
  • Provide sufficient context so that each entry can be understood on its own.
  • Be specific about names of functions, classes, modules, etc.
  • Describe when or where this is relevant
  • Use indicative and present tense. For example, write "Provide function name that does X in order to Y" over "Now X can be done by calling a new function".
• PR title adheres to conventional commit guidelines (please note that only fix: and feat: will end up in the release notes)
• If applicable: Properly documented (JSDoc of public API)
• If applicable: Check if yarn run doc still works.

[FrankEssenberger]

I think this got in by accident?

[marikaner]

Yes

[FrankEssenberger]

Is there a API to get the path? Accessing _options is potentially dangerous because this variable is not part of the public API of the request object.

[FrankEssenberger]

Perhaps a check with good logs statement in case the path is not present.

[marikaner]

will do

[marikaner]

I added a log statement. I don't think that there is another api for the request, but for extra safety I added a check that the path exists.

[FrankEssenberger]

LGTM only a minor comment.