<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/282145e9dcd0490981fbd8d45030b1a6&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/282145e9dcd0490981fbd8d45030b1a6-422bc39428aa8b45.gif</thumbnail_url><duration>73.836</duration><title>Token Consumption and Preserved Network Log</title><description>This Loom explains a token-based flow where clicking a button opens another page and the token is consumed. The speaker notes that they enabled preserve log in the network tools to capture the request to localhost along with a token sourced from the database via a token page. When opening the new window, they observe that the token no longer exists because it has been used. The Loom ends by checking storage after this token consumption.</description></oembed>