[jira] [Created] (JCLOUDS-1509) ParseAWSErrorFromXmlContent uses the default charset

Roded Bahat created JCLOUDS-1509: Summary: ParseAWSErrorFromXmlContent uses the default charset Key: JCLOUDS-1509 URL: https://issues.apache.org/jira/browse/JCLOUDS-1509 Project: jclouds Issu

[jclouds/jclouds] JCLOUDS-1509: read AWS response data with the UTF-8 charset explicitly (#1278)

AWS response data is encoded in UTF-8. Creating a String from said data using the JVM's default charset results in incorrect encoding on environments in which the JVM's default charset is not UTF-8. https://issues.apache.org/jira/browse/JCLOUDS-1509 You can view, comment on, or merge this pull req

Re: [jclouds/jclouds] JCLOUDS-1509: read AWS response data with the UTF-8 charset explicitly (#1278)

Ideally, the response should be parsed as an XML whose encoding is derived from its header. I'm not sure if that's out of scope though, since it seems that currently this code is AWS specific and UTF-8 can be expected. -- You are receiving this because you are subscribed to this thread. Reply t

[jira] [Commented] (JCLOUDS-1509) ParseAWSErrorFromXmlContent uses the default charset

[ https://issues.apache.org/jira/browse/JCLOUDS-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903070#comment-16903070 ] ASF subversion and git services commented on JCLOUDS-1509: -- Co

[jira] [Commented] (JCLOUDS-1509) ParseAWSErrorFromXmlContent uses the default charset

[ https://issues.apache.org/jira/browse/JCLOUDS-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903069#comment-16903069 ] ASF subversion and git services commented on JCLOUDS-1509: -- Co

[jira] [Commented] (JCLOUDS-1509) ParseAWSErrorFromXmlContent uses the default charset

[ https://issues.apache.org/jira/browse/JCLOUDS-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903074#comment-16903074 ] ASF subversion and git services commented on JCLOUDS-1509: -- Co

[jira] [Commented] (JCLOUDS-1509) ParseAWSErrorFromXmlContent uses the default charset

[ https://issues.apache.org/jira/browse/JCLOUDS-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903073#comment-16903073 ] ASF subversion and git services commented on JCLOUDS-1509: -- Co

[jira] [Updated] (JCLOUDS-1509) ParseAWSErrorFromXmlContent uses the default charset

[ https://issues.apache.org/jira/browse/JCLOUDS-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul updated JCLOUDS-1509: - Priority: Minor (was: Major) > ParseAWSErrorFromXmlContent uses the default charset >

[jira] [Resolved] (JCLOUDS-1509) ParseAWSErrorFromXmlContent uses the default charset

[ https://issues.apache.org/jira/browse/JCLOUDS-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul resolved JCLOUDS-1509. -- Resolution: Fixed Assignee: Andrew Gaul Fix Version/s: 2.1.3

Re: [jclouds/jclouds] JCLOUDS-1509: read AWS response data with the UTF-8 charset explicitly (#1278)

Pushed to master as a248697c0668f8f1c442b04e3833d876b125dc2c and 2.1.x as 95c4443022f9bfaa87952d5ac59befe0b89d755e. Thank you for your contribution @roded! Please use the apache/jclouds repository for future pull requests. -- You are receiving this because you modified the open/close state. R

Build failed in Jenkins: 2.1.x » jclouds-2.1.x #49

See Changes: [gaul] JCLOUDS-1509: read AWS response data with the UTF-8 charset explicitly -- [...truncated 1.45 MB...] [INFO] allblobstore ..

Re: [jclouds/jclouds] Add tag support to azure disks (#1277)

Thanks, @pimuzzo! Can you add the corresponding test in the `DiskApiMockTest`? It should be as easy as copying the existing create test and checking that the payload includes the tags. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it o

Re: [jclouds/jclouds] JCLOUDS-1509: read AWS response data with the UTF-8 charset explicitly (#1278)

Thanks @gual. Will do. -- You are receiving this because you modified the open/close state. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/1278#issuecomment-519667947

Jenkins build is back to normal : 2.1.x » jclouds-2.1.x #50

See