inspec/test/fixtures/cmd/http-remote-headers

HTTP/1.1 200 OK
Date: Tue, 03 Oct 2017 20:30:08 GMT
Expires: -1
Cache-Control: private, max-age=0
Content-Type: text/html; charset=ISO-8859-1
P3P: CP="This is not a P3P policy! See https://www.google.com/support/accounts/answer/151657?hl=en for more info."
Server: gws
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
Set-Cookie: NID=113=kNR6MIUK3vNjVH3KvQqIjfnDLLPHJ96wmC_z643weEFQ6Cfq0B2iUYqxzQk5pKVoAkbL8ZxKFvvM9v55qiNFXH_O655WuuUxPshmlSIM5xpCSH0xy09SnIQJVi0l7eKY; expires=Wed, 04-Apr-2018 20:30:08 GMT; path=/; domain=.google.com; HttpOnly
Accept-Ranges: none
Vary: Accept-Encoding
Transfer-Encoding: chunked
mock: ok

headers ok
http resource: properly execute tests on remote target (#2209) Currently, the http resource always executes locally, even when scanning a remote machine with `--target` which leads to undesireable behavior. This change adds the ability to remotely execute tests with curl. This behavior is currently opt-in with the `enable_remote_worker` flag, but will become the default behavior in InSpec 2.0. Deprecation warnings are emitted if the user is scanning a remote target but has not opted in to the new behavior. Signed-off-by: Adam Leff <adam@leff.co> 2017-10-04 20:44:09 +00:00			`HTTP/1.1 200 OK`
			`Date: Tue, 03 Oct 2017 20:30:08 GMT`
			`Expires: -1`
			`Cache-Control: private, max-age=0`
			`Content-Type: text/html; charset=ISO-8859-1`
			`P3P: CP="This is not a P3P policy! See https://www.google.com/support/accounts/answer/151657?hl=en for more info."`
			`Server: gws`
			`X-XSS-Protection: 1; mode=block`
			`X-Frame-Options: SAMEORIGIN`
			`Set-Cookie: NID=113=kNR6MIUK3vNjVH3KvQqIjfnDLLPHJ96wmC_z643weEFQ6Cfq0B2iUYqxzQk5pKVoAkbL8ZxKFvvM9v55qiNFXH_O655WuuUxPshmlSIM5xpCSH0xy09SnIQJVi0l7eKY; expires=Wed, 04-Apr-2018 20:30:08 GMT; path=/; domain=.google.com; HttpOnly`
			`Accept-Ranges: none`
			`Vary: Accept-Encoding`
			`Transfer-Encoding: chunked`
			`mock: ok`

			`headers ok`