> 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/cheating-the-cache-by-manipulating-paths.md).
# Cheating the Cache by Manipulating Paths
Cheating the Cache by Manipulating Paths notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Exploiting Path Mapping for Web Cache Deception
#### Objective of the Lab
Recover \*\* API key\*\* from user **carlos**. / Credentials provided: **wiener:peter**.
#### Observations
* In **My account** (my-account), the \*\* API key\*\* appears **in plain** for our own user.
* Initially, there is no direct indication (in the answer) that there is **caching**.
* However, by adding segments to the URL, the application continues to display the **my-account** page, suggesting a **mapping logic of routes** potentially compatible with cache.
Examples tested:
* `/my-account/TESTTTTTT` → The application always treats this as **my-account**
* `/my-account/TESTTT.js` → extension **.js** is accepted and interpreted (useful to deceive cache rules)
From the**Exploit Server**, force a victim to load a URL of the type "static" pointing to my-account:
{% code overflow="wrap" %}
```javascript
```
{% endcode %}
1. By visiting:
* `/my-account/jordan.js`/ one gets an answer that displays the \*\* carlos API key\*\*.
#### Result
The API key for **carlos** is displayed via a camouflaged URL (with `.js` extension) which allows you to take advantage of the cache/routing behavior (`/my-account/.js`).
---
# 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/cheating-the-cache-by-manipulating-paths.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)
