httpimagestore 1.8.1 → 1.9.0

data/.rspec

@@ -1 +0,0 @@
---color

data/features/cache-control.feature

@@ -1,41 +0,0 @@
-Feature: S3 object Cache-Control header settings
-	S3 objects can have Cache-Control header set during storage.
-
-	Background:
-		Given S3 settings in AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_S3_TEST_BUCKET environment variables
-		Given httpthumbnailer server is running at http://localhost:3100/health_check
-		Given httpimagestore server is running at http://localhost:3000/health_check with the following configuration
-		"""
-		s3 key="@AWS_ACCESS_KEY_ID@" secret="@AWS_SECRET_ACCESS_KEY@" ssl=false
-
-		path "hash"       "#{input_digest}.#{image_mime_extension}"
-		path "hash-name"  "#{input_digest}-#{image_name}.#{image_mime_extension}"
-
-		put "thumbnail" {
-			thumbnail "input" {
-				"no-cache"    operation="crop" width=128 height=128 format="jpeg"
-				"cache"       operation="crop" width=256 height=256 format="jpeg"
-			}
-
-			store_s3 "input"     bucket="@AWS_S3_TEST_BUCKET@" public=true path="hash"
-			store_s3 "no-cache"  bucket="@AWS_S3_TEST_BUCKET@" public=true path="hash-name"
-			store_s3 "cache"     bucket="@AWS_S3_TEST_BUCKET@" public=true path="hash-name" cache-control="public, max-age=31557600, s-maxage=0"
-		}
-		"""
-
-	@cache-control
-	Scenario: Image files get don't get Cache-Control header by default
-		Given there is no 4006450256177f4a.jpg file in S3 bucket
-		And there is no 4006450256177f4a-no-cache.jpg file in S3 bucket
-		And there is no 4006450256177f4a-cache.jpg file in S3 bucket
-		Given test.jpg file content as request body
-		When I do PUT request http://localhost:3000/thumbnail
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		OK
-		"""
-		And http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/4006450256177f4a.jpg Cache-Control header will not be set
-		And http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/4006450256177f4a-no-cache.jpg Cache-Control header will not be set
-		And http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/4006450256177f4a-cache.jpg Cache-Control header will be public, max-age=31557600, s-maxage=0

data/features/compatibility.feature

@@ -1,165 +0,0 @@
-Feature: Image list based thumbnailing and S3 storage
-	Storage based on URL specified image names to be generated and stored using two different path formats.
-	This configuration should be mostly compatible with pre v1.0 release.
-
-	Background:
-		Given S3 settings in AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_S3_TEST_BUCKET environment variables
-		Given httpthumbnailer server is running at http://localhost:3100/health_check
-		Given httpimagestore server is running at http://localhost:3000/health_check with the following configuration
-		"""
-		s3 key="@AWS_ACCESS_KEY_ID@" secret="@AWS_SECRET_ACCESS_KEY@" ssl=false
-
-		path "hash"             "#{input_digest}.#{image_mime_extension}"
-		path "hash-name"        "#{input_digest}/#{image_name}.#{image_mime_extension}"
-		path "structured"       "#{dirname}/#{input_digest}/#{basename}.#{image_mime_extension}"
-		path "structured-name"  "#{dirname}/#{input_digest}/#{basename}-#{image_name}.#{image_mime_extension}"
-		path "flexi-original"   "#{hash}.jpg"
-
-		put "thumbnail" ":name_list" ":path/.+/" {
-			thumbnail "input" {
-				"small"             operation="crop"        width=128       height=128      format="jpeg"           if-image-name-on="#{name_list}"
-				"tiny_png"          operation="crop"        width=32        height=32       format="png"            if-image-name-on="#{name_list}"
-				"bad"               operation="crop"        width=0         height=0                                if-image-name-on="#{name_list}"
-			}
-
-			store_s3 "input"     bucket="@AWS_S3_TEST_BUCKET@"   path="structured"       public=true
-			store_s3 "small"     bucket="@AWS_S3_TEST_BUCKET@"   path="structured-name"  public=true if-image-name-on="#{name_list}"
-			store_s3 "tiny_png"  bucket="@AWS_S3_TEST_BUCKET@"   path="structured-name"  public=true if-image-name-on="#{name_list}"
-
-			output_store_url {
-				"input"
-				"small"             if-image-name-on="#{name_list}"
-				"tiny_png"          if-image-name-on="#{name_list}"
-			}
-		}
-
-		put "thumbnail" ":name_list" {
-			thumbnail "input" {
-				"small"             operation="crop"        width=128       height=128      format="jpeg"   if-image-name-on="#{name_list}"
-				"tiny_png"          operation="crop"        width=32        height=32       format="png"    if-image-name-on="#{name_list}"
-			}
-
-			store_s3 "input"     bucket="@AWS_S3_TEST_BUCKET@"   path="hash"      public=true
-			store_s3 "small"     bucket="@AWS_S3_TEST_BUCKET@"   path="hash-name" public=true if-image-name-on="#{name_list}"
-			store_s3 "tiny_png"  bucket="@AWS_S3_TEST_BUCKET@"   path="hash-name" public=true if-image-name-on="#{name_list}"
-
-			output_store_url {
-				"input"
-				"small"             if-image-name-on="#{name_list}"
-				"tiny_png"          if-image-name-on="#{name_list}"
-				"bad"               if-image-name-on="#{name_list}"
-			}
-		}
-
-		# Forward compatible getting of thumbnails
-		get "thumbnail" ":hash/[0-f]{16}/" ":type/.*-square.jpg/" {
-			source_s3 "original" bucket="@AWS_S3_TEST_BUCKET@" path="flexi-original"
-			thumbnail "original" "thumbnail" operation="crop" width="50" height="50"
-			output_image "thumbnail" cache-control="public, max-age=31557600, s-maxage=0"
-		}
-
-		get "thumbnail" ":hash/[0-f]{16}/" ":type/.*-normal.jpg/" {
-			source_s3 "original" bucket="@AWS_S3_TEST_BUCKET@" path="flexi-original"
-			thumbnail "original" "thumbnail" operation="fit" width="100" height="2000"
-			output_image "thumbnail" cache-control="public, max-age=31557600, s-maxage=0"
-		}
-		"""
-
-	@compatibility
-	Scenario: Putting original and its thumbnails to S3 bucket
-		Given there is no 4006450256177f4a.jpg file in S3 bucket
-		And there is no 4006450256177f4a/small.jpg file in S3 bucket
-		And there is no 4006450256177f4a/tiny_png.png file in S3 bucket
-		Given test.jpg file content as request body
-		When I do PUT request http://localhost:3000/thumbnail/small,tiny_png
-		Then response status will be 200
-		And response content type will be text/uri-list
-		And response body will be CRLF ended lines
-		"""
-		http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/4006450256177f4a.jpg
-		http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/4006450256177f4a/small.jpg
-		http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/4006450256177f4a/tiny_png.png
-		"""
-		Then http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/4006450256177f4a.jpg will contain JPEG image of size 509x719
-		And http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/4006450256177f4a.jpg content type will be image/jpeg
-		Then http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/4006450256177f4a/small.jpg will contain JPEG image of size 128x128
-		And http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/4006450256177f4a/small.jpg content type will be image/jpeg
-		Then http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/4006450256177f4a/tiny_png.png will contain PNG image of size 32x32
-		And http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/4006450256177f4a/tiny_png.png content type will be image/png
-
-	@compatibility
-	Scenario: Putting original and its thumbnails to S3 bucket under custom path
-		Given there is no test/image/4006450256177f4a/test.jpg file in S3 bucket
-		And there is no test/image/4006450256177f4a/test-small.jpg file in S3 bucket
-		And there is no test/image/4006450256177f4a/test-tiny_png.png file in S3 bucket
-		Given test.jpg file content as request body
-		When I do PUT request http://localhost:3000/thumbnail/small,tiny_png/test/image/test
-		Then response status will be 200
-		And response content type will be text/uri-list
-		And response body will be CRLF ended lines
-		"""
-		http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/image/4006450256177f4a/test.jpg
-		http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/image/4006450256177f4a/test-small.jpg
-		http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/image/4006450256177f4a/test-tiny_png.png
-		"""
-		Then http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/image/4006450256177f4a/test.jpg will contain JPEG image of size 509x719
-		And http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/image/4006450256177f4a/test.jpg content type will be image/jpeg
-		Then http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/image/4006450256177f4a/test-small.jpg will contain JPEG image of size 128x128
-		And http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/image/4006450256177f4a/test-small.jpg content type will be image/jpeg
-		Then http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/image/4006450256177f4a/test-tiny_png.png will contain PNG image of size 32x32
-		And http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/image/4006450256177f4a/test-tiny_png.png content type will be image/png
-
-	@compatibility
-	Scenario: Input file extension should be based on content detected mime type and not on provided path
-		Given there is no test/image/4006450256177f4a/test.jpg file in S3 bucket
-		And there is no test/image/4006450256177f4a/test-tiny_png.jpg file in S3 bucket
-		Given test.jpg file content as request body
-		When I do PUT request http://localhost:3000/thumbnail/tiny_png/test/image/test.gif
-		Then response status will be 200
-		And response content type will be text/uri-list
-		And response body will be CRLF ended lines
-		"""
-		http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/image/4006450256177f4a/test.jpg
-		http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/image/4006450256177f4a/test-tiny_png.png
-		"""
-		And http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/image/4006450256177f4a/test.jpg content type will be image/jpeg
-		And http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/image/4006450256177f4a/test-tiny_png.png content type will be image/png
-
-	@compatibility
-	Scenario: Custom path name encoding when UTF-8 characters can be used
-		Given there is no test/图像/4006450256177f4a/测试.jpg file in S3 bucket
-		And there is no test/图像/4006450256177f4a/测试-small.jpg file in S3 bucket
-		Given test.jpg file content as request body
-		When I do PUT request with encoded URL http://localhost:3000/thumbnail/small/test/图像/测试
-		Then response status will be 200
-		And response content type will be text/uri-list
-		And response body will be CRLF ended lines
-		"""
-		http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/%E5%9B%BE%E5%83%8F/4006450256177f4a/%E6%B5%8B%E8%AF%95.jpg
-		http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/%E5%9B%BE%E5%83%8F/4006450256177f4a/%E6%B5%8B%E8%AF%95-small.jpg
-		"""
-		And Encoded URL http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/图像/4006450256177f4a/测试.jpg will contain JPEG image of size 509x719
-		And Encoded URL http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/test/图像/4006450256177f4a/测试-small.jpg will contain JPEG image of size 128x128
-
-	@compatibility @forward @test
-	Scenario: Getting thumbanils requested with compatibility API from flexi bucket
-			Given test.jpg file content is stored in S3 under 1234567890123456.jpg
-		When I do GET request http://localhost:3000/thumbnail/1234567890123456/foobar-blah-square.jpg
-		Then response status will be 200
-		And response content type will be image/jpeg
-		Then response body will contain JPEG image of size 50x50
-		When I do GET request http://localhost:3000/thumbnail/1234567890123456/foobar-blah-normal.jpg
-		Then response status will be 200
-		And response content type will be image/jpeg
-		Then response body will contain JPEG image of size 100x141
-
-	@compatibility
-	Scenario: Input file extension should be based on content detected mime type and not on provided path
-		Given test.jpg file content as request body
-		When I do PUT request http://localhost:3000/thumbnail/blah/test/image/test.gif
-		Then response status will be 400
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		no thumbnailing specs were selected, please use at least one of: small, tiny_png, bad
-		"""

data/features/data-uri.feature

@@ -1,55 +0,0 @@
-Feature: Data URI style image output
-	HTTP Image Store can provide images base64 encoded in data URI format so they can be included directly in HTML pages.
-
-	Background:
-		Given httpthumbnailer server is running at http://localhost:3100/health_check
-		Given httpimagestore server is running at http://localhost:3000/ with the following configuration
-		"""
-		post "data-uri" "no-identify" {
-			output_data_uri_image "input"
-		}
-
-		post "data-uri" "cache-control" {
-			identify "input"
-			output_data_uri_image "input" cache-control="public, max-age=31557600, s-maxage=0"
-		}
-
-		post "data-uri" {
-			identify "input"
-			output_data_uri_image "input"
-		}
-		"""
-
-	@data-uri
-	Scenario: Getting image encoded in data URI scheme with base64 encoding
-		Given tiny.png file content as request body
-		When I do POST request http://localhost:3000/data-uri
-		Then response status will be 200
-		And response content type will be text/uri-list
-		And response body will be
-		"""
-		data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAgAAAAICAIAAABLbSncAAAAgUlEQVQI10XNsQ2CUBhF4XOTfwJeog0U2kLJNlZOxQ4swBLGwkhhY6MNRkic4Fq8ENqTLznqhuvlOY2v5f6egaYs6iq1x30YAENdJskgEBAYUFMlYSMw2CYk2sMOkTFgI6Fp/mEpt7Ua69Sf2TRgLESMt8dW5bwE4vtZvOK8xkj8Ac8BL8dFQipPAAAAAElFTkSuQmCC
-		"""
-
-	@data-uri
-	Scenario: Getting image encoded in data URI scheme with base64 encoding - cache-control should be supported
-		Given tiny.png file content as request body
-		When I do POST request http://localhost:3000/data-uri/cache-control
-		Then response status will be 200
-		And response content type will be text/uri-list
-		And response Cache-Control will be public, max-age=31557600, s-maxage=0
-		And response body will be
-		"""
-		data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAgAAAAICAIAAABLbSncAAAAgUlEQVQI10XNsQ2CUBhF4XOTfwJeog0U2kLJNlZOxQ4swBLGwkhhY6MNRkic4Fq8ENqTLznqhuvlOY2v5f6egaYs6iq1x30YAENdJskgEBAYUFMlYSMw2CYk2sMOkTFgI6Fp/mEpt7Ua69Sf2TRgLESMt8dW5bwE4vtZvOK8xkj8Ac8BL8dFQipPAAAAAElFTkSuQmCC
-		"""
-
-	@data-uri
-	Scenario: Error 500 served when data URI output is used on unidentified image
-		Given tiny.png file content as request body
-		When I do POST request http://localhost:3000/data-uri/no-identify
-		Then response status will be 500
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		image 'input' needs to be identified first to be used in data URI output
-		"""

data/features/encoding.feature

@@ -1,103 +0,0 @@
-Feature: Encoded UTF-8 URI support
-	HTTP Image Store should be able to decode UTF-8 characters form URI using URI decode and also support JavaScript encode() format.
-
-	Background:
-		Given S3 settings in AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_S3_TEST_BUCKET environment variables
-		Given httpthumbnailer server is running at http://localhost:3100/health_check
-		Given httpimagestore server is running at http://localhost:3000/health_check with the following configuration
-		"""
-		s3 key="@AWS_ACCESS_KEY_ID@" secret="@AWS_SECRET_ACCESS_KEY@" ssl=false
-		path "path"             "#{path}"
-
-		post "file" "encoding" "encoded" {
-			store_file "input" root="/tmp" path="path"
-			output_store_uri "input" path="path"
-		}
-
-		post "file" "encoding" "decoded" {
-			store_file "input" root="/tmp" path="path"
-			output_store_path "input" path="path"
-		}
-
-		post "s3" "encoding" "encoded" {
-			store_s3 "input" bucket="@AWS_S3_TEST_BUCKET@" path="path"
-			output_store_uri "input" path="path"
-		}
-
-		post "s3" "encoding" "decoded" {
-			store_s3 "input" bucket="@AWS_S3_TEST_BUCKET@" path="path"
-			output_store_path "input" path="path"
-		}
-		"""
-
-	Scenario: JavaScript encode() + URL encoded variable decoding and URL encoding for file based storage
-		Given test.png file content as request body
-		When I do POST request http://localhost:3000/file/encoding/encoded/triple%20kro%25u0301l.png
-		And response content type will be text/uri-list
-		And response body will be CRLF ended lines
-		"""
-		/triple%20kr%C3%B3l.png
-		"""
-
-	Scenario: JavaScript encode() + URL encoded variable decoding and URL encoding for S3 based storage
-		Given test.png file content as request body
-		When I do POST request http://localhost:3000/s3/encoding/encoded/triple%20kro%25u0301l.png
-		And response content type will be text/uri-list
-		And response body will be CRLF ended lines
-		"""
-		/triple%20kr%C3%B3l.png
-		"""
-
-	Scenario: URL encoded variable decoding and URL encoding with ? for file based storage
-		Given test.png file content as request body
-		When I do POST request http://localhost:3000/file/encoding/encoded/hello%3Fworld.png
-		And response content type will be text/uri-list
-		And response body will be CRLF ended lines
-		"""
-		/hello%3Fworld.png
-		"""
-
-	Scenario: URL encoded variable decoding and URL encoding with ? for S3 based storage
-		Given test.png file content as request body
-		When I do POST request http://localhost:3000/s3/encoding/encoded/hello%3Fworld.png
-		And response content type will be text/uri-list
-		And response body will be CRLF ended lines
-		"""
-		/hello%3Fworld.png
-		"""
-
-	Scenario: URL encoded variable decoding for file based storage
-		Given test.png file content as request body
-		When I do POST request http://localhost:3000/file/encoding/decoded/triple%20kr%C3%B3l.png
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		triple król.png
-		"""
-
-	Scenario: URL encoded variable decoding for S3 based storage
-		Given test.png file content as request body
-		When I do POST request http://localhost:3000/s3/encoding/decoded/triple%20kr%C3%B3l.png
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		triple król.png
-		"""
-
-	Scenario: URL path normalization with ? for file based storage
-		Given test.png file content as request body
-		When I do POST request http://localhost:3000/file/encoding/decoded/hello%3Fworld.png
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		hello?world.png
-		"""
-
-	Scenario: URL path normalization with ? S3 file based storage
-		Given test.png file content as request body
-		When I do POST request http://localhost:3000/s3/encoding/decoded/hello%3Fworld.png
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		hello?world.png
-		"""

data/features/error-reporting.feature

@@ -1,281 +0,0 @@
-Feature: Error handling
-	API should provide different status codes with text/plain description body for different error modes.
-
-	Background:
-		Given S3 settings in AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_S3_TEST_BUCKET environment variables
-		Given httpthumbnailer server is running at http://localhost:3100/health_check
-		Given httpimagestore server is running at http://localhost:3000/health_check with the following configuration
-		"""
-		s3 key="@AWS_ACCESS_KEY_ID@" secret="@AWS_SECRET_ACCESS_KEY@" ssl=false
-
-		path "uri_part"     "/thumbnails/#{input_digest}/#{name}.#{image_mime_extension}"
-		path "structured-name"  "#{dirname}/#{input_digest}/#{basename}-#{image_name}.#{image_mime_extension}"
-		path "missing"          "blah"
-		path "zero"             "zero"
-		path "hash"     "#{input_digest}"
-
-		put "multipart" ":name_list" {
-			thumbnail "input" {
-				"small"             operation="crop"        width=128       height=128                              if-image-name-on="#{name_list}"
-				"bad"               operation="crop"        width=0         height=0                                if-image-name-on="#{name_list}"
-				"bad_dim"           operation="crop"        width="128x"    height=128                              if-image-name-on="#{name_list}"
-				"superlarge"        operation="crop"        width=16000     height=16000                            if-image-name-on="#{name_list}"
-				"large_png"         operation="crop"        width=7000      height=7000     format="png"            if-image-name-on="#{name_list}"
-				"bad_opts"          operation="crop"        width=128       height=128      options="foo=bar"       if-image-name-on="#{name_list}"
-			}
-		}
-
-		put "singlepart" ":name_list" {
-			thumbnail "input"    "small"         operation="crop"        width=128       height=128                              if-image-name-on="#{name_list}"
-			thumbnail "input"    "bad"           operation="crop"        width=0         height=0                                if-image-name-on="#{name_list}"
-			thumbnail "input"    "bad_dim"       operation="crop"        width="128x"    height=128                              if-image-name-on="#{name_list}"
-			thumbnail "input"    "superlarge"    operation="crop"        width=16000     height=16000                            if-image-name-on="#{name_list}"
-			thumbnail "input"    "large_png"     operation="crop"        width=7000      height=7000     format="png"            if-image-name-on="#{name_list}"
-			thumbnail "input"    "bad_opts"      operation="crop"        width=128       height=128      options="foo=bar"       if-image-name-on="#{name_list}"
-		}
-
-		post "filename" "/(?<name>.+?)(\\.[^\\.]+)?$/" {
-			identify "input"
-			store_s3 "input" bucket="@AWS_S3_TEST_BUCKET@" path="hash" cache-root="/tmp"
-			output_store_path "input" path="uri_part"
-		}
-
-		get "s3" {
-			source_s3 "original" bucket="@AWS_S3_TEST_BUCKET@" path="missing"
-		}
-
-		get "file" {
-			source_file "original" root="/tmp" path="missing"
-		}
-
-		get "zero" {
-			source_file "original" root="/dev" path="zero"
-		}
-
-		path "not_defined" "#{bogous}"
-		get "not_defined" {
-			source_file "original" root="/tmp" path="not_defined"
-		}
-
-		path "body" "#{input_digest}"
-		get "body" {
-			source_file "original" root="/tmp" path="body"
-		}
-
-		path "no_image_meta" "#{image_mime_extension}"
-		put "no_image_meta" {
-			store_file "input" root="/tmp" path="no_image_meta"
-		}
-		"""
-
-	@error-reporting
-	Scenario: Reporting of missing resource
-		When I do GET request http://localhost:3000/blah
-		Then response status will be 404
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		request for URI '/blah' was not handled by the server
-		"""
-
-	@error-reporting
-	Scenario: Reporting of missing S3 resource
-		When I do GET request http://localhost:3000/s3
-		Then response status will be 404
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		S3 bucket 'httpimagestoretest' does not contain key 'blah'
-		"""
-
-	@error-reporting
-	Scenario: Reporting of missing file resource
-		When I do GET request http://localhost:3000/file
-		Then response status will be 404
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		error while processing image 'original': file 'blah' not found
-		"""
-
-	@error-reporting
-	Scenario: Reporting of unsupported media type
-		Given test.txt file content as request body
-		When I do PUT request http://localhost:3000/multipart/small,tiny
-		Then response status will be 415
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		thumbnailing of 'input' failed: unsupported media type: no decode delegate for this image format
-		"""
-		When I do PUT request http://localhost:3000/singlepart/small,tiny
-		Then response status will be 415
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		thumbnailing of 'input' into 'small' failed: unsupported media type: no decode delegate for this image format
-		"""
-
-	@error-reporting
-	Scenario: Reporting and handling of thumbnailing errors
-		Given test.jpg file content as request body
-		When I do PUT request http://localhost:3000/multipart/small,bad
-		Then response status will be 400
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		thumbnailing of 'input' into 'bad' failed: at least one image dimension is zero: 0x0
-		"""
-		When I do PUT request http://localhost:3000/singlepart/small,bad
-		Then response status will be 400
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		thumbnailing of 'input' into 'bad' failed: at least one image dimension is zero: 0x0
-		"""
-
-	@error-reporting
-	Scenario: Reporting and handling of thumbnailing errors - bad options format
-		Given test.jpg file content as request body
-		When I do PUT request http://localhost:3000/multipart/small,bad_opts
-		Then response status will be 400
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		thumbnailing of 'input' into 'bad_opts' failed: missing option value for key 'foo=bar'
-		"""
-		When I do PUT request http://localhost:3000/singlepart/small,bad_opts
-		Then response status will be 400
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		thumbnailing of 'input' into 'bad_opts' failed: missing option value for key 'foo=bar'
-		"""
-
-	@error-reporting @test
-	Scenario: Bad dimension
-		Given test.jpg file content as request body
-		When I do PUT request http://localhost:3000/multipart/bad_dim
-		Then response status will be 400
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		thumbnailing of 'input' into 'bad_dim' failed: bad dimension value: 128x
-		"""
-		When I do PUT request http://localhost:3000/singlepart/bad_dim
-		Then response status will be 400
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		thumbnailing of 'input' into 'bad_dim' failed: bad dimension value: 128x
-		"""
-
-	@error-reporting @413 @load
-	Scenario: Too large image - uploaded image too big to fit in memory limit
-		Given test-large.jpg file content as request body
-		When I do PUT request http://localhost:3000/multipart/large_png
-		Then response status will be 413
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		thumbnailing of 'input' failed: image too large: cache resources exhausted
-		"""
-		When I do PUT request http://localhost:3000/singlepart/large_png
-		Then response status will be 413
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		thumbnailing of 'input' into 'large_png' failed: image too large: cache resources exhausted
-		"""
-
-	@error-reporting @413 @thumbnail
-	Scenario: Too large image - memory exhausted when thmbnailing
-		Given test.jpg file content as request body
-		When I do PUT request http://localhost:3000/multipart/superlarge
-		Then response status will be 413
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		thumbnailing of 'input' into 'superlarge' failed: image too large: cache resources exhausted
-		"""
-		When I do PUT request http://localhost:3000/singlepart/superlarge
-		Then response status will be 413
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		thumbnailing of 'input' into 'superlarge' failed: image too large: cache resources exhausted
-		"""
-
-	@error-reporting
-	Scenario: Bad URI encoding
-		Given test.jpg file content as request body
-		When I do POST request http://localhost:3000/filename/hello%e9world.jpg
-		Then response status will be 400
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		invalid UTF-8 encoding in URI: "hello\\xE9world"
-		"""
-
-	@error-reporting
-	Scenario: Bad URI encoding + JavaScript encode
-		Given test.jpg file content as request body
-		When I do POST request http://localhost:3000/filename/triple%20kro%25udfcfl.png
-		Then response status will be 400
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		invalid UTF-8 encoding in URI: "triple kro\\xED\\xBF\\x8Fl"
-		"""
-
-	@error-reporting
-	Scenario: Zero body length
-		Given test.empty file content as request body
-		When I do PUT request http://localhost:3000/multipart/small
-		Then response status will be 400
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		empty body - expected image data
-		"""
-
-	@error-reporting
-	Scenario: Memory limit exceeded
-		When I do GET request http://localhost:3000/zero
-		Then response status will be 413
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		memory limit exceeded
-		"""
-
-	@error-reporting @variables
-	Scenario: Bad variable use - not defined
-		When I do GET request http://localhost:3000/not_defined
-		Then response status will be 500
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		cannot generate path 'not_defined' from template '\#{bogous}': variable 'bogous' not defined
-		"""
-
-	@error-reporting @variables
-	Scenario: Bad variable use - no body
-		When I do GET request http://localhost:3000/body
-		Then response status will be 500
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		cannot generate path 'body' from template '#{input_digest}': need not empty request body to generate value for 'input_digest'
-		"""
-
-	@error-reporting @variables
-	Scenario: Bad variable use - no image meta
-		Given test.jpg file content as request body
-		When I do PUT request http://localhost:3000/no_image_meta
-		Then response status will be 500
-		And response content type will be text/plain
-		And response body will be CRLF ended lines like
-		"""
-		cannot generate path 'no_image_meta' from template '#{image_mime_extension}': image 'input' does not have data for variable 'image_mime_extension'
-		"""