FPS callerReference vs CallerReference #1095

Closed
cariaso opened this Issue Nov 4, 2012 · 3 comments

Comments

Projects
None yet
2 participants
Contributor

cariaso commented Nov 4, 2012

#909
the error message shown in that bug report and page 12 of
http://awsdocs.s3.amazonaws.com/FPS/latest/fps-gsg.pdf
both show that the correct parameter name is callerReference, without the first letter being capitalized, however line 79 of
https://github.com/boto/boto/blob/master/boto/fps/connection.py
shows the fix uses a capital letter.

Presumably amazon is tolerant of both, but my existing codes which already supply a callerReference, are being mangled by the addition of a second param with the alternate capitalization.

Contributor

cariaso commented Nov 5, 2012

Despite the above, switching to the lowercase form, now seems to cause amazon to reject the request. I'm nearly certain that was not the behavior from their servers previously.

Contributor

disruptek commented Nov 5, 2012

Please test https://github.com/disruptek/boto/tree/fps_callerreference and let me know whether that simple fix solves your problem.

Contributor

cariaso commented Nov 5, 2012

It does not. I can only explain what I'm seeing as a change on amazon's servers, which seems very unlikely. I will make the necessary adjustments on my side.

@cariaso cariaso closed this Nov 5, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment