Adam Baldwin

Forge format files in branch, repository and checkout directories if a 403 or 404 is detected.

File names with spaces from git ls-files are not handled properly when trying to check out the files after the resource reference have been pulled down.

To get files outside of the repo look in .gitignore, at minimum parse it out in a sane URL format so it could be brute forced with dirbuster or the...

Implement object history retrieval via the git log --follow technique (deep retrieval) www.example.com adambaldwin$ git log --follow -p tools.php fatal: unable to read source tree (3263cb705eab41f85559e01a2592665508f4a227) getsha 3263cb705eab41f85559e01a2592665508f4a227

Do not write out 404 message to files that 404

1

404 error content is put into the requested file instead of simply moving on. Do not write out content that has 404's Example is BZR hates this The requested URL...

404 on robots.txt should fail to allow not error

1

I'm thinking that a 404 on a robots.txt file should fail into an always allow state. I'm not sure if there is a standard behavior a bot should follow if...

I get an exception when parsing the following robots.txt. robots.txt: ``` Sitemap: http://rebeccasugar.tumblr.com/sitemap1.xml User-agent: * Disallow: /private Disallow: /random Disallow: /day Crawl-delay: 1 ``` ``` site: http://rebeccasugar.tumblr.com/ /Users/adam_baldwin/Documents/projects/millimeter/node_modules/robotstxt/index.js:305 return myGateKeeper.sitemaps.push({...