httpimagestore 1.8.1 → 1.9.0

data/features/flexi.feature

@@ -1,259 +0,0 @@
-Feature: Flexible API with two storage options and Facebook like thumbnailing URL format
-	Features two storage approaches: with JPEG conversion and limiting in size - for user provided content - and storing as is.
-	POST requests will end up with server side generated storage key based on input data digest.
-	PUT requests can be used to store image under provided storage key.
-	Thumbnail GET API is similar to described in https://developers.facebook.com/docs/reference/api/using-pictures/#sizes.
-	Stored object extension and content type is determined from image data.
-
-	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 "path" "#{path}"
-
-		## User uploaded content - always JPEG converted, not bigger than 2160x2160 and in hight quality compression
-		post "pictures" {
-			thumbnail "input" "original" operation="limit" width=2160 height=2160 format="jpeg" quality=95
-			store_s3 "original" bucket="@AWS_S3_TEST_BUCKET@" path="hash"
-			output_store_path "original"
-		}
-
-		put "pictures" {
-			thumbnail "input" "original" operation="limit" width=2160 height=2160 format="jpeg" quality=95
-			store_s3 "original" bucket="@AWS_S3_TEST_BUCKET@" path="path"
-			output_store_path "original"
-		}
-
-		## Uploaded by us for use on the website - whatever we send
-		post "images" {
-			identify "input"
-			store_s3 "input" bucket="@AWS_S3_TEST_BUCKET@" path="hash"
-			output_store_path "input"
-		}
-
-		put "images" {
-			identify "input"
-			store_s3 "input" bucket="@AWS_S3_TEST_BUCKET@" path="path"
-			output_store_path "input"
-		}
-
-		## Thumbailing - keep input format; default JPEG quality is 85
-		get "pictures" "&:width" "&:height" "&:operation?crop" "&:background-color?white" {
-			source_s3 "original" bucket="@AWS_S3_TEST_BUCKET@" path="path"
-			thumbnail "original" "thumbnail" operation="#{operation}" width="#{width}" height="#{height}" options="background-color:#{background-color}"
-			output_image "thumbnail" cache-control="public, max-age=31557600, s-maxage=0"
-		}
-
-		get "pictures" "&:width" "&:height?1080" "&:operation?fit" "&:background-color?white" {
-			source_s3 "original" bucket="@AWS_S3_TEST_BUCKET@" path="path"
-			thumbnail "original" "thumbnail" operation="#{operation}" width="#{width}" height="#{height}" options="background-color:#{background-color}"
-			output_image "thumbnail" cache-control="public, max-age=31557600, s-maxage=0"
-		}
-
-		get "pictures" "&:height" "&:width?1080" "&:operation?fit" "&:background-color?white" {
-			source_s3 "original" bucket="@AWS_S3_TEST_BUCKET@" path="path"
-			thumbnail "original" "thumbnail" operation="#{operation}" width="#{width}" height="#{height}" options="background-color:#{background-color}"
-			output_image "thumbnail" cache-control="public, max-age=31557600, s-maxage=0"
-		}
-
-		get "pictures" "&type=square" {
-			source_s3 "original" bucket="@AWS_S3_TEST_BUCKET@" path="path"
-			thumbnail "original" "thumbnail" operation="crop" width="50" height="50"
-			output_image "thumbnail" cache-control="public, max-age=31557600, s-maxage=0"
-		}
-
-		get "pictures" "&type=small" {
-			source_s3 "original" bucket="@AWS_S3_TEST_BUCKET@" path="path"
-			thumbnail "original" "thumbnail" operation="fit" width="50" height="2000"
-			output_image "thumbnail" cache-control="public, max-age=31557600, s-maxage=0"
-		}
-
-		get "pictures" "&type=normall" {
-			source_s3 "original" bucket="@AWS_S3_TEST_BUCKET@" path="path"
-			thumbnail "original" "thumbnail" operation="fit" width="100" height="2000"
-			output_image "thumbnail" cache-control="public, max-age=31557600, s-maxage=0"
-		}
-
-		get "pictures" "&type=large" {
-			source_s3 "original" bucket="@AWS_S3_TEST_BUCKET@" path="path"
-			thumbnail "original" "thumbnail" operation="fit" width="200" height="2000"
-			output_image "thumbnail" cache-control="public, max-age=31557600, s-maxage=0"
-		}
-
-		## By default serve original image
-		get "pictures" {
-			source_s3 "original" bucket="@AWS_S3_TEST_BUCKET@" path="path"
-			output_image "original" cache-control="public, max-age=31557600, s-maxage=0"
-		}
-		"""
-
-	@flexi @pictures @post
-	Scenario: Posting picture to S3 bucket will store it under input data digest, limit to 2160x1260 and converted to JPEG
-		Given there is no 625d51a1820b607f.jpg file in S3 bucket
-		Given test-large.jpg file content as request body
-		When I do POST request http://localhost:3000/pictures
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		625d51a1820b607f.jpg
-		"""
-		Then S3 object 625d51a1820b607f.jpg will contain JPEG image of size 1529x2160
-		Then S3 object 625d51a1820b607f.jpg content type will be image/jpeg
-		When I do GET request http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/625d51a1820b607f.jpg
-		Then response status will be 403
-		Given there is no b0fe25319ba5909a.jpg file in S3 bucket
-		Given test.png file content as request body
-		When I do POST request http://localhost:3000/pictures
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		b0fe25319ba5909a.jpg
-		"""
-		Then S3 object b0fe25319ba5909a.jpg will contain JPEG image of size 509x719
-		Then S3 object b0fe25319ba5909a.jpg content type will be image/jpeg
-		When I do GET request http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/b0fe25319ba5909a.jpg
-		Then response status will be 403
-
-	@flexi @pictures @put
-	Scenario: Putting picture to S3 bucket will store it under provided path, limit it to 2160x1260 and converted to JPEG
-		Given there is no hello/world file in S3 bucket
-		Given test-large.jpg file content as request body
-		When I do PUT request http://localhost:3000/pictures/hello/world
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		hello/world
-		"""
-		Then S3 object hello/world will contain JPEG image of size 1529x2160
-		Then S3 object hello/world content type will be image/jpeg
-		When I do GET request http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/hello/world
-		Then response status will be 403
-		Given test.png file content as request body
-		When I do PUT request http://localhost:3000/pictures/hello/world
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		hello/world
-		"""
-		Then S3 object hello/world will contain JPEG image of size 509x719
-		Then S3 object hello/world content type will be image/jpeg
-		When I do GET request http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/hello/world
-		Then response status will be 403
-
-	@flexi @images @post
-	Scenario: Posting picture to S3 bucket will store it under first input data digest
-		Given there is no b0fe25319ba5909a.png file in S3 bucket
-		Given test.png file content as request body
-		When I do POST request http://localhost:3000/images
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		b0fe25319ba5909a.png
-		"""
-		Then S3 object b0fe25319ba5909a.png will contain PNG image of size 509x719
-		Then S3 object b0fe25319ba5909a.png content type will be image/png
-		When I do GET request http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/b0fe25319ba5909a.png
-		Then response status will be 403
-
-	@flexi @images @put
-	Scenario: Putting picture to S3 bucket will store it under provided path
-		Given there is no hello/world file in S3 bucket
-		Given test.png file content as request body
-		When I do PUT request http://localhost:3000/images/hello/world
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		hello/world
-		"""
-		Then S3 object hello/world will contain PNG image of size 509x719
-		Then S3 object hello/world content type will be image/png
-		When I do GET request http://@AWS_S3_TEST_BUCKET@.s3.amazonaws.com/hello/world
-		Then response status will be 403
-
-	@flexi @default
-	Scenario: Getting stored image when no query string param is present
-		Given test.png file content as request body
-		When I do PUT request http://localhost:3000/images/test.png
-		And I do GET request http://localhost:3000/pictures/test.png
-		Then response status will be 200
-		And response content type will be image/png
-		Then response body will contain PNG image of size 509x719
-		Given test.jpg file content as request body
-		When I do PUT request http://localhost:3000/images/test.jpg
-		And I do GET request http://localhost:3000/pictures/test.jpg
-		Then response status will be 200
-		And response content type will be image/jpeg
-		Then response body will contain JPEG image of size 509x719
-
-	@flexi @type
-	Scenario: Getting square type tumbnail
-		Given test.png file content as request body
-		When I do PUT request http://localhost:3000/images/test.png
-		And I do GET request http://localhost:3000/pictures/test.png?type=square
-		Then response status will be 200
-		And response content type will be image/png
-		Then response body will contain PNG image of size 50x50
-
-	@flexi @type
-	Scenario: Getting small type tumbnail
-		Given test.png file content as request body
-		When I do PUT request http://localhost:3000/images/test.png
-		And I do GET request http://localhost:3000/pictures/test.png?type=small
-		Then response status will be 200
-		And response content type will be image/png
-		Then response body will contain PNG image of size 50x71
-
-	@flexi @type
-	Scenario: Getting normall type tumbnail
-		Given test.png file content as request body
-		When I do PUT request http://localhost:3000/images/test.png
-		And I do GET request http://localhost:3000/pictures/test.png?type=normall
-		Then response status will be 200
-		And response content type will be image/png
-		Then response body will contain PNG image of size 100x141
-
-	@flexi @type
-	Scenario: Getting large type tumbnail
-		Given test.png file content as request body
-		When I do PUT request http://localhost:3000/images/test.png
-		And I do GET request http://localhost:3000/pictures/test.png?type=large
-		Then response status will be 200
-		And response content type will be image/png
-		Then response body will contain PNG image of size 200x283
-
-	@flexi @size
-	Scenario: Getting custom size tumbnail
-		Given test.png file content as request body
-		When I do PUT request http://localhost:3000/images/test.png
-		And I do GET request http://localhost:3000/pictures/test.png?width=123&height=321
-		Then response status will be 200
-		And response content type will be image/png
-		Then response body will contain PNG image of size 123x321
-
-	@flexi @size
-	Scenario: Getting custom size tumbnail without height
-		Given test.png file content as request body
-		When I do PUT request http://localhost:3000/images/test.png
-		And I do GET request http://localhost:3000/pictures/test.png?width=123
-		Then response status will be 200
-		And response content type will be image/png
-		Then response body will contain PNG image of size 123x174
-
-	@flexi @size
-	Scenario: Getting custom size tumbnail without width
-		Given test.png file content as request body
-		When I do PUT request http://localhost:3000/images/test.png
-		And I do GET request http://localhost:3000/pictures/test.png?height=321
-		Then response status will be 200
-		And response content type will be image/png
-		Then response body will contain PNG image of size 227x321

data/features/health-check.feature

@@ -1,29 +0,0 @@
-Feature: Health check URL
-	Server can be tested with GET request to '/health_check'.
-
-	Background:
-		Given httpimagestore server is running at http://localhost:3000/ with the following configuration
-		"""
-		"""
-
-	@health-check
-	Scenario: Passing health check when thumbnailer is running
-		Given httpthumbnailer server is running at http://localhost:3100/
-		When I do GET request http://localhost:3000/health_check
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		HTTP Image Store OK
-		"""
-
-	@health-check
-	Scenario: Failing health check when thumbnailer is not running
-		Given httpthumbnailer server is not running
-		When I do GET request http://localhost:3000/health_check
-		Then response status will be 502
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		Connection refused - connect(2) (http://localhost:3100)
-		"""

data/features/request-matching.feature

@@ -1,211 +0,0 @@
-Feature: Request matching
-	Incoming requests needs to be matched in flexible way and appropriate data needs to be available in form of variables used to parametrize processing.
-
-	Background:
-		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
-		"""
-		# URI segment matchers
-		get "string" {
-			output_text "path: '#{path}'"
-		}
-
-		get "any" "default" ":test1" ":test2?foo" ":test3?bar" ":test4?baz" {
-			output_text "test1: '#{test1}' test2: '#{test2}' test3: '#{test3}' test4: '#{test4}' path: '#{path}'"
-		}
-		get "any" ":test1" ":test2" {
-			output_text "test1: '#{test1}' test2: '#{test2}' path: '#{path}'"
-		}
-
-		get "regexp1" ":test1/a.c/" ":test2/.*/" {
-			output_text "test1: '#{test1}' test2: '#{test2}' path: '#{path}'"
-		}
-		get "regexp-404" ":test1/a.c.*/" ":test2/\\./" {
-			output_text "test1: '#{test1}' test2: '#{test2}' path: '#{path}'"
-		}
-
-		get "regexp" "named" "/(?<test1>..)-(?<test2>..)/" ":test3/.*/" {
-			output_text "test1: '#{test1}' test2: '#{test2}' test3: '#{test3}' path: '#{path}'"
-		}
-		get "regexp" "named" "nocapture" "/..-../" {
-			output_text "path: '#{path}'"
-		}
-		get "regexp" "named" "bad1" "/(?<test1>..)-(?<test1>..)/" ":test3/.*/" {
-			output_text "test1: '#{test1}' test2: '#{test2}' test3: '#{test3}' path: '#{path}'"
-		}
-		get "regexp" "named" "bad2" "/(?<test1>..)-(?<test1>..)/" ":test3/.*/" {
-			output_text "test1: '#{test1}' test3: '#{test3}' path: '#{path}'"
-		}
-
-		# Query string matchers
-		get "query" "key-value" "&hello=world" {
-			output_text "query key-value matched path: '#{path}'"
-		}
-
-		get "query" "key" "default" "&:hello?abc" {
-			output_text "key: '#{hello}' path: '#{path}'"
-		}
-		get "query" "key" "&:hello" {
-			output_text "key: '#{hello}' path: '#{path}'"
-		}
-		get "query" "options" {
-			output_text "query_string_options: '#{query_string_options}' path: '#{path}'"
-		}
-		"""
-
-	@request-matching @string
-	Scenario: Matching URI segment with strings
-		When I do GET request http://localhost:3000/string/hello/world
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		path: 'hello/world'
-		"""
-
-	@request-matching @capture-any
-	Scenario: Capturing any URI segment
-		When I do GET request http://localhost:3000/any/foo/bar/hello/world
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		test1: 'foo' test2: 'bar' path: 'hello/world'
-		"""
-
-	@request-matching @capture-any-default
-	Scenario: Capturing any URI segment with default value
-		When I do GET request http://localhost:3000/any/default/foo/bar
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		test1: 'foo' test2: 'bar' test3: 'bar' test4: 'baz' path: ''
-		"""
-
-	@request-matching @capture-regexp
-	Scenario: Capturing URI segment with regexp match
-		When I do GET request http://localhost:3000/regexp1/abc/foobar/hello/world
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		test1: 'abc' test2: 'foobar/hello/world' path: ''
-		"""
-		When I do GET request http://localhost:3000/regexp2/abc/foobar/hello/world
-		Then response status will be 404
-
-	@request-matching @capture-named-regexp
-	Scenario: Capturing URI segment with named regexp match
-		When I do GET request http://localhost:3000/regexp/named/ab-12/hello/world
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		test1: 'ab' test2: '12' test3: 'hello/world' path: ''
-		"""
-		When I do GET request http://localhost:3000/regexp/named/nocapture/ab-12/hello/world
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		path: 'hello/world'
-		"""
-		When I do GET request http://localhost:3000/regexp/named/ab-12
-		Then response status will be 404
-		When I do GET request http://localhost:3000/regexp/named/ab-123/hello/world
-		Then response status will be 404
-		When I do GET request http://localhost:3000/regexp/named/bad1/ab-12/hello/world
-		Then response status will be 500
-		When I do GET request http://localhost:3000/regexp/named/bad2/ab-12/hello/world
-		Then response status will be 500
-		And response body will be CRLF ended lines
-		"""
-		matched more arguments than named (3 for 2)
-		"""
-
-	@request-matching @query-key-value
-	Scenario: Capturing URI by presence of given key-value query string pair
-		When I do GET request http://localhost:3000/query/key-value/hello/world?hello=world
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		query key-value matched path: 'hello/world'
-		"""
-		When I do GET request http://localhost:3000/query/key-value/hello/world?foo=bar&hello=world&bar=baz
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		query key-value matched path: 'hello/world'
-		"""
-		When I do GET request http://localhost:3000/query/key-value/hello/world
-		Then response status will be 404
-		When I do GET request http://localhost:3000/query/key-value/hello/world?hello=Xorld
-		Then response status will be 404
-		When I do GET request http://localhost:3000/query/key-value/hello/world?heXlo=world
-		Then response status will be 404
-
-	@request-matching @query-key
-	Scenario: Capturing URI by query string key presence
-		When I do GET request http://localhost:3000/query/key/hello/world?hello=world
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		key: 'world' path: 'hello/world'
-		"""
-		When I do GET request http://localhost:3000/query/key/hello/world?foo=bar&hello=foobar&bar=baz
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		key: 'foobar' path: 'hello/world'
-		"""
-		When I do GET request http://localhost:3000/query/key/hello/world
-		Then response status will be 404
-		When I do GET request http://localhost:3000/query/key/hello/world?heXlo=world
-		Then response status will be 404
-
-	@request-matching @query-key-default
-	Scenario: Capturing URI by query string key presence
-		When I do GET request http://localhost:3000/query/key/default/hello/world?hello=world
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		key: 'world' path: 'hello/world'
-		"""
-		When I do GET request http://localhost:3000/query/key/default/hello/world?foo=bar&hello=foobar&bar=baz
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		key: 'foobar' path: 'hello/world'
-		"""
-		When I do GET request http://localhost:3000/query/key/default/hello/world
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		key: 'abc' path: 'hello/world'
-		"""
-		When I do GET request http://localhost:3000/query/key/default/hello/world?heXlo=world
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		key: 'abc' path: 'hello/world'
-		"""
-
-	@request-matching @query-string-options
-	Scenario: URI query string key-value pairs should always be available as query_string_options variable
-		When I do GET request http://localhost:3000/query/options/hello/world?foo=hello&bar=world
-		Then response status will be 200
-		And response content type will be text/plain
-		And response body will be CRLF ended lines
-		"""
-		query_string_options: 'bar:world,foo:hello' path: 'hello/world'
-		"""
-