Image sometimes not created...

[laddi]

I have set up a server to handle resizes of images stored in an S3 folder. The problem is that some images are not resized at all but return with a grey image with a red 'x' at the top left. And to frustrate me even further, the log has no indication of what is wrong and returns a 200.

Example: http://crater.greenqloud.com/fit/?size=200x200&url=https://s.greenqloud.com/laddih-default/Photos/2002/2-Innflutningspart%C3%AD/Svana%20og%20Þórunn.jpg?Expires=1361376965&AWSAccessKeyId=RFdLVGdmWk9hWkZQempESVc4RG5ybkhPOFU3WFE2&Signature=sS4VLAZyYYDn8ERyPlwXL9iImRc%3D

Is this a problem with the server or maybe with node-imageable module?

[sdepold]

Is it possible that the images aren't world readible?

Am 20.02.2013 um 16:26 schrieb "Þórhallur Helgason" <
[email protected]>:

I have set up a server to handle resizes of images stored in an S3 folder.
The problem is that some images are not resized at all but return with a
grey image with a red 'x' at the top left. And to frustrate me even
further, the log has no indication of what is wrong and returns a 200.

Example:
http://crater.greenqloud.com/fit/?size=200x200&url=https://s.greenqloud.com/laddih-default/Photos/2002/2-Innflutningspart%C3%AD/Svana%20og%20Þórunn.jpg?Expires=1361376965&AWSAccessKeyId=RFdLVGdmWk9hWkZQempESVc4RG5ybkhPOFU3WFE2&Signature=sS4VLAZyYYDn8ERyPlwXL9iImRc%3Dhttp://crater.greenqloud.com/fit/?size=200x200&url=https://s.greenqloud.com/laddih-default/Photos/2002/2-Innflutningspart%C3%AD/Svana%20og%20%C3%9E%C3%B3runn.jpg?Expires=1361376965&AWSAccessKeyId=RFdLVGdmWk9hWkZQempESVc4RG5ybkhPOFU3WFE2&Signature=sS4VLAZyYYDn8ERyPlwXL9iImRc%3D

Is this a problem with the server or maybe with node-imageable module?

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/2.

[sdepold]

The scenario described by you is actually a feature and not a bug. It
indicates that the original source is not available.

Am 20.02.2013 um 16:26 schrieb "Þórhallur Helgason" <
[email protected]>:

I have set up a server to handle resizes of images stored in an S3 folder.
The problem is that some images are not resized at all but return with a
grey image with a red 'x' at the top left. And to frustrate me even
further, the log has no indication of what is wrong and returns a 200.

Example:
http://crater.greenqloud.com/fit/?size=200x200&url=https://s.greenqloud.com/laddih-default/Photos/2002/2-Innflutningspart%C3%AD/Svana%20og%20Þórunn.jpg?Expires=1361376965&AWSAccessKeyId=RFdLVGdmWk9hWkZQempESVc4RG5ybkhPOFU3WFE2&Signature=sS4VLAZyYYDn8ERyPlwXL9iImRc%3Dhttp://crater.greenqloud.com/fit/?size=200x200&url=https://s.greenqloud.com/laddih-default/Photos/2002/2-Innflutningspart%C3%AD/Svana%20og%20%C3%9E%C3%B3runn.jpg?Expires=1361376965&AWSAccessKeyId=RFdLVGdmWk9hWkZQempESVc4RG5ybkhPOFU3WFE2&Signature=sS4VLAZyYYDn8ERyPlwXL9iImRc%3D

Is this a problem with the server or maybe with node-imageable module?

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/2.

[sdepold]

Ah wait. U didnt encodeURIComponent'ed the url of the image.

Am 20.02.2013 um 16:26 schrieb "Þórhallur Helgason" <
[email protected]>:

I have set up a server to handle resizes of images stored in an S3 folder.
The problem is that some images are not resized at all but return with a
grey image with a red 'x' at the top left. And to frustrate me even
further, the log has no indication of what is wrong and returns a 200.

Example:
http://crater.greenqloud.com/fit/?size=200x200&url=https://s.greenqloud.com/laddih-default/Photos/2002/2-Innflutningspart%C3%AD/Svana%20og%20Þórunn.jpg?Expires=1361376965&AWSAccessKeyId=RFdLVGdmWk9hWkZQempESVc4RG5ybkhPOFU3WFE2&Signature=sS4VLAZyYYDn8ERyPlwXL9iImRc%3Dhttp://crater.greenqloud.com/fit/?size=200x200&url=https://s.greenqloud.com/laddih-default/Photos/2002/2-Innflutningspart%C3%AD/Svana%20og%20%C3%9E%C3%B3runn.jpg?Expires=1361376965&AWSAccessKeyId=RFdLVGdmWk9hWkZQempESVc4RG5ybkhPOFU3WFE2&Signature=sS4VLAZyYYDn8ERyPlwXL9iImRc%3D

Is this a problem with the server or maybe with node-imageable module?

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/2.

[laddi]

Hi, you are 100% correct! Added encodeURI to the url, problem solved! Thanks a million! :D

[sdepold]

Great!

Von meinem iPad gesendet

Am 20.02.2013 um 17:08 schrieb Þórhallur Helgason [email protected]:

Hi, you are 100% correct! Added encodeURI to the url, problem solved! Thanks a million! :D

—
Reply to this email directly or view it on GitHub.

[laddi]

One question though, since I reached you: How can I maximize the throughput on the server (handle as many requests as possible)?

[sdepold]

Well that depends on your server environment. As the module spawns imagemagick process you'll need either many small servers or some with fast cpu's. We used ec2 micro instances with 3 to 5 concurrent request per node. This was managed by an haproxy instance in front of each node app.

[laddi]

OK, I'm gonna see what I can conjure up! :)

We are gonna use this for the sharing feature of our S3 compatible storage system. You can check it out on greenqloud.com (create a 7 day free trial on my.greenqloud.com).

[sdepold]

Nice page :)

Von meinem iPad gesendet

Am 20.02.2013 um 18:01 schrieb Þórhallur Helgason [email protected]:

OK, I'm gonna see what I can conjure up! :)

We are gonna use this for the sharing feature of our S3 compatible storage system. You can check it out on greenqloud.com (create a 7 day free trial on my.greenqloud.com).

—
Reply to this email directly or view it on GitHub.

[laddi]

Another question, adding an Expires header to the created image. Any setting for that?