RE: Why is HttpAmazonS3Helper client side only
Hi Stuart, Sounds great! I would just suggest that you contribute patches for this based Restlet 2.0 code (SVN trunk) as we can't add new features to Restlet 1.1 branch. Of course, you can still use your own local patches for 1.1 if needed for your own project. Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -Message d'origine- De : Stuart MacKay [mailto:smac...@flagstonesoftware.com] Envoyé : lundi 1 juin 2009 13:54 À : discuss@restlet.tigris.org Objet : Re: Why is HttpAmazonS3Helper client side only Jerome, From what I understand so far I think the server side implementation should be as simple as implementing the authenticate() method in com.noelios.restlet.authenticationHttpAmazonS3Helper so it calls the key Resolver and then generates the signature to compare with the incoming request. Once I get it working I will be happy to contribute the code. Best Regards, Stuart MacKay Flagstone Software Ltd. > Hi Stuart, > > The common use case so far has been to invoke Amazon Web services not to > implement some. But, there is no special reason for now support that on the > server-side as well. > > Would you be interested in contributing such as feature? > > Regarding the choice of Tomcat versus alternatives such as Jetty, there is > really nothing specific to Restlet. Your Restlet application should work > equally well in all those containers. > > Best regards, > Jerome Louvel > -- > Restlet ~ Founder and Lead developer ~ http://www.restlet.org > Noelios Technologies ~ Co-founder ~ http://www.noelios.com > > > -Message d'origine- > De : Stuart MacKay [mailto:smac...@flagstonesoftware.com] > Envoyé : jeudi 28 mai 2009 00:38 > À : discuss@restlet.tigris.org > Objet : Why is HttpAmazonS3Helper client side only > > The authentication of requests using HMAC-SHA1 seems to be an obvious > win for server applications. So after trying to implement it in my test > app, then digging through the source code I find that HttpAmazonS3Helper > is client side only ? > > Is there a specific reason why this is the case ? Is it covered by a > patent ? If not then is it possible to implement such a scheme when > using Tomcat 6 as a container ? > > BTW Are there any considered opinions why Tomcat may or may not be a > good choice for a restlet container ? > > Stuart > > -- > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=23559 > 64 > > -- > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2357453 > > -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2357477 -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2357636
Re: Why is HttpAmazonS3Helper client side only
Jerome, From what I understand so far I think the server side implementation should be as simple as implementing the authenticate() method in com.noelios.restlet.authenticationHttpAmazonS3Helper so it calls the key Resolver and then generates the signature to compare with the incoming request. Once I get it working I will be happy to contribute the code. Best Regards, Stuart MacKay Flagstone Software Ltd. > Hi Stuart, > > The common use case so far has been to invoke Amazon Web services not to > implement some. But, there is no special reason for now support that on the > server-side as well. > > Would you be interested in contributing such as feature? > > Regarding the choice of Tomcat versus alternatives such as Jetty, there is > really nothing specific to Restlet. Your Restlet application should work > equally well in all those containers. > > Best regards, > Jerome Louvel > -- > Restlet ~ Founder and Lead developer ~ http://www.restlet.org > Noelios Technologies ~ Co-founder ~ http://www.noelios.com > > > -Message d'origine- > De : Stuart MacKay [mailto:smac...@flagstonesoftware.com] > Envoyé : jeudi 28 mai 2009 00:38 > À : discuss@restlet.tigris.org > Objet : Why is HttpAmazonS3Helper client side only > > The authentication of requests using HMAC-SHA1 seems to be an obvious > win for server applications. So after trying to implement it in my test > app, then digging through the source code I find that HttpAmazonS3Helper > is client side only ? > > Is there a specific reason why this is the case ? Is it covered by a > patent ? If not then is it possible to implement such a scheme when > using Tomcat 6 as a container ? > > BTW Are there any considered opinions why Tomcat may or may not be a > good choice for a restlet container ? > > Stuart > > -- > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=23559 > 64 > > -- > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2357453 > > -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2357477
RE: Why is HttpAmazonS3Helper client side only
Hi Stuart, The common use case so far has been to invoke Amazon Web services not to implement some. But, there is no special reason for now support that on the server-side as well. Would you be interested in contributing such as feature? Regarding the choice of Tomcat versus alternatives such as Jetty, there is really nothing specific to Restlet. Your Restlet application should work equally well in all those containers. Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -Message d'origine- De : Stuart MacKay [mailto:smac...@flagstonesoftware.com] Envoyé : jeudi 28 mai 2009 00:38 À : discuss@restlet.tigris.org Objet : Why is HttpAmazonS3Helper client side only The authentication of requests using HMAC-SHA1 seems to be an obvious win for server applications. So after trying to implement it in my test app, then digging through the source code I find that HttpAmazonS3Helper is client side only ? Is there a specific reason why this is the case ? Is it covered by a patent ? If not then is it possible to implement such a scheme when using Tomcat 6 as a container ? BTW Are there any considered opinions why Tomcat may or may not be a good choice for a restlet container ? Stuart -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=23559 64 -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2357453
Why is HttpAmazonS3Helper client side only
The authentication of requests using HMAC-SHA1 seems to be an obvious win for server applications. So after trying to implement it in my test app, then digging through the source code I find that HttpAmazonS3Helper is client side only ? Is there a specific reason why this is the case ? Is it covered by a patent ? If not then is it possible to implement such a scheme when using Tomcat 6 as a container ? BTW Are there any considered opinions why Tomcat may or may not be a good choice for a restlet container ? Stuart -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2355964
RE: Bug in HttpAmazonS3Helper class
Hi Jerome, No problems at all. Thanks for fixing it so quickly. Kind regards, Matt Hi Matt, Thanks for reporting this. I've fixed the bug (due to an evolution in S3) in both 1.1 branch and SVN trunk. I've also added proper unit test cases to make sure there is no regression. Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -Message d'origine- De : MattyJ [mailto:mjwat...@gmail.com] Envoyé : vendredi 10 avril 2009 02:14 À : discuss@restlet.tigris.org Objet : Bug in HttpAmazonS3Helper class Ok. I think I've figured out my the problem with the HttpAmazonS3Helper class. The code in the method getCanonicalizedResourceName(Reference resourceRef) isn't quite correct as It needs to incorporate the _bucketname_ into the path. Presently its just getting the resource path. >From the S3 developer guide examples: GET /photos/puppy.jpg HTTP/1.1 Host: _bucketname_.s3.amazonaws.com Date: Tue, 27 Mar 2007 19:36:42 + Authorization: AWS 0PN5J17HBGZHT7JJ3X82: xXjDGYUmKxnwqr5KXNPGldn5LbA= Which should translate into the following string to sign: GET\n \n \n Tue, 27 Mar 2007 19:36:42 +\n /_bucketname_/photos/puppy.jpg Matt. -- View this message in context: http://n2.nabble.com/Bug-in-HttpAmazonS3Helper-class-tp2614094p2614094.html Sent from the Restlet Discuss mailing list archive at Nabble.com. -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=16205 18 -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1733047 -- View this message in context: http://n2.nabble.com/Bug-in-HttpAmazonS3Helper-class-tp2614094p2660703.html Sent from the Restlet Discuss mailing list archive at Nabble.com. -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1813266
RE: Bug in HttpAmazonS3Helper class
Hi Matt, Thanks for reporting this. I've fixed the bug (due to an evolution in S3) in both 1.1 branch and SVN trunk. I've also added proper unit test cases to make sure there is no regression. Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -Message d'origine- De : MattyJ [mailto:mjwat...@gmail.com] Envoyé : vendredi 10 avril 2009 02:14 À : discuss@restlet.tigris.org Objet : Bug in HttpAmazonS3Helper class Ok. I think I've figured out my the problem with the HttpAmazonS3Helper class. The code in the method getCanonicalizedResourceName(Reference resourceRef) isn't quite correct as It needs to incorporate the _bucketname_ into the path. Presently its just getting the resource path. >From the S3 developer guide examples: GET /photos/puppy.jpg HTTP/1.1 Host: _bucketname_.s3.amazonaws.com Date: Tue, 27 Mar 2007 19:36:42 + Authorization: AWS 0PN5J17HBGZHT7JJ3X82: xXjDGYUmKxnwqr5KXNPGldn5LbA= Which should translate into the following string to sign: GET\n \n \n Tue, 27 Mar 2007 19:36:42 +\n /_bucketname_/photos/puppy.jpg Matt. -- View this message in context: http://n2.nabble.com/Bug-in-HttpAmazonS3Helper-class-tp2614094p2614094.html Sent from the Restlet Discuss mailing list archive at Nabble.com. -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=16205 18 -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1733047
Bug in HttpAmazonS3Helper class
Ok. I think I've figured out my the problem with the HttpAmazonS3Helper class. The code in the method getCanonicalizedResourceName(Reference resourceRef) isn't quite correct as It needs to incorporate the _bucketname_ into the path. Presently its just getting the resource path. >From the S3 developer guide examples: GET /photos/puppy.jpg HTTP/1.1 Host: _bucketname_.s3.amazonaws.com Date: Tue, 27 Mar 2007 19:36:42 + Authorization: AWS 0PN5J17HBGZHT7JJ3X82: xXjDGYUmKxnwqr5KXNPGldn5LbA= Which should translate into the following string to sign: GET\n \n \n Tue, 27 Mar 2007 19:36:42 +\n /_bucketname_/photos/puppy.jpg Matt. -- View this message in context: http://n2.nabble.com/Bug-in-HttpAmazonS3Helper-class-tp2614094p2614094.html Sent from the Restlet Discuss mailing list archive at Nabble.com. -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1620518
HttpAmazonS3Helper
Can someone give me an example on how to use the HttpAmazonS3Helper class? Thanks in advance, Matt -- View this message in context: http://n2.nabble.com/HttpAmazonS3Helper-tp2609388p2609388.html Sent from the Restlet Discuss mailing list archive at Nabble.com. -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1608094
