> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/web/web-cache-deception/web-cache-deception-with-path-delimiters.md).
# Web Cache Deception with Path Delimiters
Web Cache Deception with Path Delimiters notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Exploiting Path Delimiters for Web Cache Deception
#### Context
**Lab:** Operation path limits for web cache deception / **Objective:** recover the \*\* API key\*\* from user **carlos**. / **Access provided:** possible connection with `wiener:peter`. / **Help:** a list of possible delimiters is provided by the lab.
#### Initial Observation
* On the **My account** page, we see a sign that clearly displays our own API key\*\*.
* In the background, normal access triggers a request:
```bash
GET /my-account HTTP/2
```
In this case, **the answer is not served from the cache** (no visible/interpreted cache behavior).
#### Test of Delimiters
* By adding a \*\* semicolon\*\* `;` in the path, the \*\* application still interprets the route\*\* to `my-account`, but this time **with cache behavior**.
Using **Intruder**, we check several delimiters, and we find that **the semicolon works**.
Example of a valid path:
* `/my-account;test.js`
#### Exploitation
Purpose: Make sure that the victim visits a trapped URL to make the **/my-account** response \*\* cached\*\* and then reread it with another variant to get the **carlos** data.
From the**Exploit Server**, the victim is redirected to:
```javascript
```
#### Recovery of API Key
* Then we change the URL and access:
* `/my-account;jordan.js`
This answer then contains **the carlos API key**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/web/web-cache-deception/web-cache-deception-with-path-delimiters.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media)
