- From: Colin PUY <notifications@github.com>
- Date: Mon, 31 Jul 2017 11:23:49 +0000 (UTC)
- To: whatwg/xhr <xhr@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 31 July 2017 11:24:12 UTC
@mnot getting csrf token from response header is not the "right" way to do as well. Anyway I'm just here to expose how my legacy app has been impacted by xhr API break and how it put my company in danger. Up to you to decide whether or not you'll keep this change -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/xhr/issues/146#issuecomment-319040573
Received on Monday, 31 July 2017 11:24:12 UTC