-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide better error message for invalid endpoint urls #899
Labels
feature-request
A feature should be added or improved.
Comments
jamesls
added a commit
to jamesls/aws-cli
that referenced
this issue
Aug 27, 2014
jamesls
added a commit
to jamesls/aws-cli
that referenced
this issue
Aug 27, 2014
jamesls
added a commit
that referenced
this issue
Aug 27, 2014
* validate-endpoint-url: Add #899 to CHANGELOG Provide better error message for invalid endpoint urls
Closed
kyleknap
added a commit
that referenced
this issue
Sep 11, 2014
* release-1.4.3: (24 commits) Bumping version to 1.4.3 Updated the changelog for new features. EMR: Remove UnknownApplicationError EMR: Update modify-cluster-attributes error message. Fixed s3 to s3 sync urlencoding pagniation bug. Add #899 to CHANGELOG Provide better error message for invalid endpoint urls Fixed the ``s3 website help`` command. Throw error when too few args are passed to s3. Enabled ``--page-size`` as global argument. Add entry to changelog Fixed a Windows integration test. Error out for remaining args in custom commands Fixed tests when user is the root. EMR: Update help text and examples. 1. Add helptext description, which says leaving instance-count creates one node cluster; 2. Sanitizing add-tags example 3. Edit/change example text for create-cluster and add-tags Added Windows compatibility to warning about files. Enabled skipping and warning special files. Added support for warning about and skipping files. Update changelog Add support for struct with list param shorthand ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The error message could provide more context about what exactly went wrong with the request. For example:
A better error message would be something like:
The text was updated successfully, but these errors were encountered: