# Request interception and HTTP token capture

This PR contains two quick fixes regarding request interception and HTTP token capture.

**Request interception:**

Likely a regression introduced by [e3bef94](https://github.com/kgretzky/evilginx2/commit/e3bef9433c3cc95d3e523533e498c834506739f0), as the value of `req.Host` does not contain the phishing hostname anymore at the new location but holds the legitimate one. As a result, the comparison fails and the request is not intercepted.

**HTTP token capture:**

The header is indeed captured in the request (e,g,. `Authorization` header). I just added the check on the domain and path specified in the phishlet (`v.domain` and `v.path`).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://rproxylab.gitbook.io/evilginx-lab-by-cfs0x/basics/modified-extensions/request-interception-and-http-token-capture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.