Archiveteam/grab-site
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

README: Remove instructions for grabbing a site that requires a cookie because the --header solution results in the cookie being sent to all domains instead of just the intended domain

Browse Source
This commit is contained in:
Ivan Kozik 2015-10-20 10:50:18 +00:00
parent 77248eb47c
commit 3dfb9dc757
1 changed files with 0 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
README.md
View File

@ -245,26 +245,6 @@ You may want to pipe the output to `sort` and `less`:
Grabbing a site that requires a cookie
---
1. Log into the site in Chrome.
2. Open the developer tools with F12.
3. Switch to the **Network** tab of the developer tools.
4. Hit F5 to reload the page. The developer tools will stay open and capture the HTTP requests.
5. Scroll up in the list of network events and click on the first request.
6. In the right pane, click the **Headers** tab.
7. Scroll down to the **Request Headers** section.
8. Copy the **Cookie:** value.
9. Start grab-site with:
```
grab-site --wpull-args="--header=\"Cookie: COOKIE_VALUE\"" URL
```
Note: do **not** use `document.cookie` in the developer tools **Console** because it does not include `HttpOnly` cookies.
Stopping a crawl
---
You can `touch DIR/stop` or press ctrl-c, which will do the same. You will