Gist 82e5b38e9a37eec15ec3cb5c1cf5382a

100%

Gist 82e5b38e9a37eec15ec3cb5c1cf5382a

✓ Published0🌍 Public

Last edited Aug 7, 2018

Created on Aug 7, 2018

This example demonstrates how to secure Laravel AJAX requests by embedding a CSRF token in the page metadata. It shows the token being generated server-side via `{{ csrf_token() }}` and placed inside a `<meta name="csrf-token">` tag for asynchronous JavaScript calls. The code highlights that the token is unique per session and must be included in every AJAX request, though Laravel allows disabling this protection, which is not recommended. The example uses Laravel’s Blade templating syntax to inject the token into the HTML.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 6caf9fb33f0b7bf1fe0b594b403dc053

This example demonstrates a potential security exploit rather than a data visualization. The PHP code generates an HTML script tag that uses JavaScript to send the visitor’s cookies to a remote webhook URL via an img request. It relies on the `document.cookie` API to capture cookie data and the `document.write` method to inject the tracking pixel. The rendering approach is purely client-side, with no charting or visualization libraries involved. The piece highlights how insecure code can misuse basic web technologies for data exfiltration.

PPeleke

55% match

Loading thumbnail…

Gist 6ed3f84640838d8320f6b209b1628e41

This example demonstrates a cross-site scripting (XSS) proof-of-concept that exfiltrates a visitor’s cookies. The code uses a raw JavaScript payload with `document.write` to inject an `<img>` tag, which fires a request to a user-supplied Ngrok URL, appending `document.cookie` as a query parameter. It shows a simple, direct attack vector for testing XSS vulnerabilities, relying on the browser’s automatic image request to send data to an external server. The visualization is the code itself, presented as a threat-modeling sample rather than a chart.

PPeleke

53% match

Loading thumbnail…

Gist 055a86617685691db7632fcb10fb8bc8

This example demonstrates a simulated cross-site scripting (XSS) attack via remote file inclusion, visually rendering a PHP script’s output as an alert dialog that exposes `document.cookie`. The visualization uses a plain HTML page to embed the PHP snippet, with the code directly echoing a `<script>` tag that triggers the alert. It relies on the browser’s native JavaScript execution rather than external libraries, showing the raw mechanism of injecting client-side code through a server-side include. The rendering approach is minimal, presenting the source code and its resulting runtime behavior side by side.

PPeleke

53% match

Loading thumbnail…

Gist 7232670

This example demonstrates how a single-page application skeleton is transformed from a static document into an interactive, AJAX-driven experience. The visualization shows a list of user-submitted code entries, with each entry dynamically loaded and rendered without a full page refresh. The implementation uses jQuery’s `$.ajax` method to fetch the `lucky_ajax.md` file and other resources, then updates the DOM with the retrieved content. The code also relies on JavaScript’s `Promise` API for handling asynchronous responses, and highlights the use of `XMLHttpRequest` for network communication. The data source is the downloaded application skeleton, whose structure is revealed through the fetched files. The example focuses on the interaction between client-side scripting and server responses.

EElaineYu

52% match

Loading thumbnail…

Gist 1bf39e5b3d6f193272ae7662fecbca1b

This example presents a procedural tutorial for generating Laravel models and migrations, emphasizing the correct creation order for Project, Category, and Level models. The visualization shows a command-line workflow using PHP’s Artisan CLI, where each `php artisan make:model` call includes the `-m` flag to simultaneously create a migration. It highlights that Project must be generated before Category and Level because the latter two contain foreign keys referencing the Project’s structure. The rendering relies on plain text and shell command formatting, with no graphical charting libraries or data-binding APIs involved.

MMistyBlunch

52% match

Loading thumbnail…

Gist c2007066af4a2f2b97d4293778f8af5d

This Scala example demonstrates a complete JWT (JSON Web Token) lifecycle, creating a signed token with custom claims and then verifying and decoding it. The code generates an ES256 key pair using `GeneratorKeyFactory` from the Ubirch crypto library, then encodes a token with `Jwt.encode` that includes tenant, device, UUID identifiers, and custom role claims, before decoding it back with `Jwt.decodeRawAll` to display the parsed header, payload, and signature. The visualized output is the `Try` result showing the extracted JSON claims alongside the cryptographic signature.

CCarlos-Augusto

52% match

Loading thumbnail…

axios interceptors for refresh token

This example shows an Axios response interceptor that automatically handles expired access tokens by refreshing them when a request returns a 401 status. The code intercepts the failed request, checks the stored refresh token from `window.localStorage`, and posts it to an authentication endpoint at `localhost:8000/auth/refresh`. On success, it updates both the access and refresh tokens in local storage, sets the new authorization header for subsequent requests, and retries the original request. The implementation uses `axios.interceptors.response.use` with a `_retry` flag to prevent infinite loops, while relying on the browser’s local storage for token persistence and Axios’s promise-based API for asynchronous flow.

AAbhay-Joshi-Git

51% match

Loading thumbnail…

Gist 1b1889baaec2adffe574

This example demonstrates a WordPress theme’s strategy for optimizing CSS delivery by inlining critical styles and asynchronously loading the full stylesheet. It shows how PHP hooks like `wp_head` and `wp_footer` conditionally inject scripts, styles, and a cookie-based cache check. The code uses `file_get_contents` to embed JavaScript files such as `loadCSS.js` and `onloadCSS.js`, alongside a `<style>` block for critical CSS. A `noscript` fallback ensures the full stylesheet loads without JavaScript. The implementation relies on the `Roots\Sage\Assets` namespace and functions like `asset_path()` to resolve file paths.

GGolodhros

50% match