{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Why Global Fetch Defaults Can Leak API Tokens","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/bd75ae8f\"></iframe>","width":"100%","height":180,"duration":220,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/why-global-fetch-defaults-can-leak-api-tokens.\nGlobal API defaults can silently leak auth headers across services. Here’s how isolated client configs prevent that risk.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #fetch, #api, #http-client, #axios, #fetch-wrapper, #global-defaults, #token-leakage, #axios-defaults,  and more.\nThis story was written by: @toufiq. Learn more about this writer by checking @toufiq's about page,\n            and for more stories, please visit hackernoon.com.\nGlobal API defaults can silently leak auth headers across services. Here’s how isolated client configs prevent that risk.\n        \n        ","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}