rightscale / right_api_client

84%

master: 85%

LAST BUILD ON BRANCH rest-client-lockdown

branch: rest-client-lockdown

CHANGE BRANCH

x

Reset

• rest-client-lockdown
• add_coveralls_support
• master
• v1.5.22
• cm_14_15_acu176188_oauth_refresh
• oauth_refresh
• qama_14_13_acu182727_hide_credentials_no_monkey_patch
• cm_14_20_acu182886_trac19374_rest_client_gem_freeze_version_1_6_7
• cm_cow
• cm_14_21_acu183852_suppress_warnings
• v1.5.23
• v1.5.24
• update_default_ssl_ver_to_latest
• need_login
• right_script_fixes
• v1.5.25
• re_login_error_response_code_fix
• v1.5.26
• qastia_15_02_update_readme_maintainer_error_message_from_rest_client
• consume-api15-metadata
• fix_audit_entry_detail_encoding
• IV-1711_set_6_minute_timeout
• v1.5.27
• support_put_runnable_bindings
• IV-3008_update_rightscript_plain_text
• release128
• v1.5.28
• IV-3165_using_rl10_local_proxy
• IV-3209_deprecate_support_for_ruby_1_x
• v1.6.0
• v1.6.1
• IV-3209_update_readme_versioning_change
• fix_timeout
• GOV-291
• IV-4671_arm_support
• OPS-3543_handle_empty_string
• IV-4997_handle_empty_200_misbehavior
• v1.6.2
• CLSLY-979_Use_json_2_gem_in_right_api_client
• v1.6.3

Forbid rest-client 1.8

rest-client 1.8 drops existing cookies on redirection:
<https://github.com/rest-client/rest-client/issues/406>

This means that if you use the RightScale API Client to try to log in to
'my.rightscale.com' with a session cookie from 'us-4.rightscale.com' (or
vice versa), then the cookie will be dropped and you won't be able to
access the API, even if the cookie is valid.