diff options
| author | onefang | 2019-09-29 11:22:34 +1000 |
|---|---|---|
| committer | onefang | 2019-09-29 11:22:34 +1000 |
| commit | 37df809ec7a43c964bdede49d4dd4f95d910c42c (patch) | |
| tree | 810a7fa24305302f014f091e31f7e45255eea134 | |
| parent | CheckRedirects() -> checkRedirects() (diff) | |
| download | apt-panopticon-37df809ec7a43c964bdede49d4dd4f95d910c42c.zip apt-panopticon-37df809ec7a43c964bdede49d4dd4f95d910c42c.tar.gz apt-panopticon-37df809ec7a43c964bdede49d4dd4f95d910c42c.tar.bz2 apt-panopticon-37df809ec7a43c964bdede49d4dd4f95d910c42c.tar.xz | |
Oops, read the "redir" logic incorrectly, and wrote the theory section wrong.
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
| @@ -254,6 +254,6 @@ the IP, with a Host header set to the original host name. Redirects will | |||
| 254 | not be followed by that request. If the request returns a redirect, then | 254 | not be followed by that request. If the request returns a redirect, then |
| 255 | checkURL() is called recursively. If the redirect is to some host we are | 255 | checkURL() is called recursively. If the redirect is to some host we are |
| 256 | not already checking, we call checkRedirects() on it, with an IP of | 256 | not already checking, we call checkRedirects() on it, with an IP of |
| 257 | "redir". This causes checkRedirects() to bypass the IP gathering | 257 | "redir". This causes checkRedirects() to bypass the test that would |
| 258 | process, and call checkPaths() with the new host. | 258 | otherwise call checkPaths(), instead gathering the IPs and fork as usual. |
| 259 | 259 | ||