-
Notifications
You must be signed in to change notification settings - Fork 52
XML instead of JSON reply #25
Comments
The boto fix was a minor fix for cqs and you can currently use cqs with boto. We are aware of the remaining issues with boto and cns: Basically boto sns uses the undocumented ContentType=JSON parameter to receive JSON encoded responses from AWS and CMB currently does not support that. The same question has come up before and we may add JSON support to CNS in the next release to be compatible. |
Thanks for replying so quickly. For others who are also having this ContentType=JSON problem, there is a patch for boto Unfortunately, it is based on a 2 year old version of boto (2.5.1) |
Boris and I have actually been chatting about this. I could merge in the upstream and re-attempt the pull request but there is no guarantee that the pull request will be merged (it wasn't 2 years ago when there was no conflicts). At least with adding the ContentType we have control of that change while there are no guarantees with boto. My fork should work with CNS, and if there are issues I will fix those in the fork. |
Hi Derek, thanks for pitching in. I did try replacing boto 2.25.0 with your boto fork, but I have not managed to test the CNS feature since the python app I have been given seemed to require some functions in newer boto releases. For example, it made some S3 calls using your boto fork before CNS calls and could not find functions like boto.s3.regions():
As you mentioned quite rightly, it might be easier to add ContentType=JSON to CMB than patching boto. Kind regards, Jane. |
Hi,
Thanks for developing CMB and making it open source.
I just started playing with it and discovered that it is returning XML instead of JSON to my SNS requests (sent via the python aws library boto).
For example, BOTO sent out something like:
CMB replied with some XML, like:
AWS replied with some JSON, like:
As a result, boto worked ok with AWS but returned this error with CMB:
I am already using the latest CMB on github with the boto fix (06baa74).
Any suggestion or insight into this problem much appreciated.
Kind regards,
Jane
The text was updated successfully, but these errors were encountered: