This repository has been archived on 2020-03-24. You can view files and clone it, but cannot push or open issues or pull requests.

Matt Jibson b3c2388618 Allow setting of boto's S3 host for SIGv4 ... The problem only happens when a user has configured the new AWS Frankfurt region for their S3 backend. It is the only region to require the new v4 signature. All other regions support both v2 and v4. I'm not sure which version is used by default on US Standard. We could attempt to figure out where the bucket is hosted based on its DNS resolution and auto-populate the host field that way. But I think the amount of effort to have that work correctly outweighs its benefit for such a simple solution. fixes #863 fixes #764		2015-11-18 17:19:33 -05:00
..
css	Merge master into vulnerability-tool	2015-11-12 21:52:47 -05:00
directives	Switch blog and docs to https	2015-11-13 12:29:48 -05:00
img	Vulnerability UI part 2	2015-11-12 16:59:36 -05:00
js	Allow setting of boto's S3 host for SIGv4	2015-11-18 17:19:33 -05:00
lib	Switch to using an aggregated logs query and infinite scrolling	2015-07-31 16:38:02 -04:00
partials	Vulnerability UI part 2	2015-11-12 16:59:36 -05:00
standalonelib	Enable DEBUGGING mode, which loads the individual script files rather than the minimized bundles created by grunt	2014-04-15 16:35:15 -04:00
tutorial	Tutorial improvements	2015-06-04 14:15:47 -04:00
robots.txt	Change default robots.txt to disallow everything; we now override it in the production config	2015-06-17 15:45:03 -04:00
sitemap.xml	Strip whitespace from ALL the things.	2014-11-24 16:07:38 -05:00