Bucket names in S3 not being created with spaces or special characters anymore
I use android to upload files to S3 in my app. When I was using the sdk version 2.6.+, my buckets were created with spaces and special characters without any problem. But after I upgraded my versions of S3 and SQS in gradle to 2.7.+, my buckets now have the characters of URL. The spaces now are %20, for example.
I really need my buckets stay with spaces and special characters, but from android side I've found anything that could help me, and I don't know much about S3.
Can someone help me please? Only to remember, the only thing I've done was upgrade the version of sdk and I can't downgrade it.
android amazon-s3 asked Nov 19 '18 at 21:03
alexVongolaalexVongola
113
add a comment |
I use android to upload files to S3 in my app. When I was using the sdk version 2.6.+, my buckets were created with spaces and special characters without any problem. But after I upgraded my versions of S3 and SQS in gradle to 2.7.+, my buckets now have the characters of URL. The spaces now are %20, for example.
I really need my buckets stay with spaces and special characters, but from android side I've found anything that could help me, and I don't know much about S3.
Can someone help me please? Only to remember, the only thing I've done was upgrade the version of sdk and I can't downgrade it.
android amazon-s3 asked Nov 19 '18 at 21:03
alexVongolaalexVongola
113
1
Which region are you using? Traditionally,us-east-1permitted non-DNS compliant names, while other regions required DNS-compliant names so that bucket names could be used in URLs (egmybucket.s3.amazonaws.com).
– John Rotenstein
Nov 19 '18 at 22:30
I'm using us-east-1 region @JohnRotenstein
– alexVongola
Nov 20 '18 at 17:00
add a comment |
I use android to upload files to S3 in my app. When I was using the sdk version 2.6.+, my buckets were created with spaces and special characters without any problem. But after I upgraded my versions of S3 and SQS in gradle to 2.7.+, my buckets now have the characters of URL. The spaces now are %20, for example.
I really need my buckets stay with spaces and special characters, but from android side I've found anything that could help me, and I don't know much about S3.
Can someone help me please? Only to remember, the only thing I've done was upgrade the version of sdk and I can't downgrade it.
android amazon-s3 asked Nov 19 '18 at 21:03
alexVongolaalexVongola
113
I use android to upload files to S3 in my app. When I was using the sdk version 2.6.+, my buckets were created with spaces and special characters without any problem. But after I upgraded my versions of S3 and SQS in gradle to 2.7.+, my buckets now have the characters of URL. The spaces now are %20, for example.
I really need my buckets stay with spaces and special characters, but from android side I've found anything that could help me, and I don't know much about S3.
Can someone help me please? Only to remember, the only thing I've done was upgrade the version of sdk and I can't downgrade it.
android amazon-s3 android amazon-s3 asked Nov 19 '18 at 21:03
alexVongolaalexVongola
113
asked Nov 19 '18 at 21:03
alexVongolaalexVongola
113
asked Nov 19 '18 at 21:03
alexVongolaalexVongola
113
asked Nov 19 '18 at 21:03
alexVongolaalexVongola
113
asked Nov 19 '18 at 21:03
alexVongolaalexVongola
113
113
1
Which region are you using? Traditionally,us-east-1permitted non-DNS compliant names, while other regions required DNS-compliant names so that bucket names could be used in URLs (egmybucket.s3.amazonaws.com).
– John Rotenstein
Nov 19 '18 at 22:30
I'm using us-east-1 region @JohnRotenstein
– alexVongola
Nov 20 '18 at 17:00
add a comment |
1
Which region are you using? Traditionally,us-east-1permitted non-DNS compliant names, while other regions required DNS-compliant names so that bucket names could be used in URLs (egmybucket.s3.amazonaws.com).
– John Rotenstein
Nov 19 '18 at 22:30
I'm using us-east-1 region @JohnRotenstein
– alexVongola
Nov 20 '18 at 17:00
1
1
Which region are you using? Traditionally,
us-east-1 permitted non-DNS compliant names, while other regions required DNS-compliant names so that bucket names could be used in URLs (eg mybucket.s3.amazonaws.com).– John Rotenstein
Nov 19 '18 at 22:30
Which region are you using? Traditionally,
us-east-1 permitted non-DNS compliant names, while other regions required DNS-compliant names so that bucket names could be used in URLs (eg mybucket.s3.amazonaws.com).– John Rotenstein
Nov 19 '18 at 22:30
I'm using us-east-1 region @JohnRotenstein
– alexVongola
Nov 20 '18 at 17:00
I'm using us-east-1 region @JohnRotenstein
– alexVongola
Nov 20 '18 at 17:00
add a comment |
1 Answer
1
active
oldest
votes
Are you using 2.7.4 or 2.7.5? If so, this fix in 2.7.6 may help. Fixed the regression introduced in 2.7.4 to support transfer objects with name containing special characters.
answered Nov 20 '18 at 2:54
DonDon
111
Didn't work. I've tried with 2.7.6, 2.8.2 and 2.8.3 and none of that worked with special characters :( In my transferUtility.upload function I can see that the address is going with the special characters without any problem, but in S3 the problem still happens
– alexVongola
Nov 20 '18 at 17:18
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53382586%2fbucket-names-in-s3-not-being-created-with-spaces-or-special-characters-anymore%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Are you using 2.7.4 or 2.7.5? If so, this fix in 2.7.6 may help. Fixed the regression introduced in 2.7.4 to support transfer objects with name containing special characters.
answered Nov 20 '18 at 2:54
DonDon
111
Didn't work. I've tried with 2.7.6, 2.8.2 and 2.8.3 and none of that worked with special characters :( In my transferUtility.upload function I can see that the address is going with the special characters without any problem, but in S3 the problem still happens
– alexVongola
Nov 20 '18 at 17:18
add a comment |
Are you using 2.7.4 or 2.7.5? If so, this fix in 2.7.6 may help. Fixed the regression introduced in 2.7.4 to support transfer objects with name containing special characters.
answered Nov 20 '18 at 2:54
DonDon
111
Didn't work. I've tried with 2.7.6, 2.8.2 and 2.8.3 and none of that worked with special characters :( In my transferUtility.upload function I can see that the address is going with the special characters without any problem, but in S3 the problem still happens
– alexVongola
Nov 20 '18 at 17:18
add a comment |
Are you using 2.7.4 or 2.7.5? If so, this fix in 2.7.6 may help. Fixed the regression introduced in 2.7.4 to support transfer objects with name containing special characters.
answered Nov 20 '18 at 2:54
DonDon
111
Are you using 2.7.4 or 2.7.5? If so, this fix in 2.7.6 may help. Fixed the regression introduced in 2.7.4 to support transfer objects with name containing special characters.
answered Nov 20 '18 at 2:54
DonDon
111
answered Nov 20 '18 at 2:54
DonDon
111
answered Nov 20 '18 at 2:54
DonDon
111
answered Nov 20 '18 at 2:54
DonDon
111
111
Didn't work. I've tried with 2.7.6, 2.8.2 and 2.8.3 and none of that worked with special characters :( In my transferUtility.upload function I can see that the address is going with the special characters without any problem, but in S3 the problem still happens
– alexVongola
Nov 20 '18 at 17:18
add a comment |
Didn't work. I've tried with 2.7.6, 2.8.2 and 2.8.3 and none of that worked with special characters :( In my transferUtility.upload function I can see that the address is going with the special characters without any problem, but in S3 the problem still happens
– alexVongola
Nov 20 '18 at 17:18
Didn't work. I've tried with 2.7.6, 2.8.2 and 2.8.3 and none of that worked with special characters :( In my transferUtility.upload function I can see that the address is going with the special characters without any problem, but in S3 the problem still happens
– alexVongola
Nov 20 '18 at 17:18
Didn't work. I've tried with 2.7.6, 2.8.2 and 2.8.3 and none of that worked with special characters :( In my transferUtility.upload function I can see that the address is going with the special characters without any problem, but in S3 the problem still happens
– alexVongola
Nov 20 '18 at 17:18
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53382586%2fbucket-names-in-s3-not-being-created-with-spaces-or-special-characters-anymore%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Which region are you using? Traditionally,
us-east-1permitted non-DNS compliant names, while other regions required DNS-compliant names so that bucket names could be used in URLs (egmybucket.s3.amazonaws.com).– John Rotenstein
Nov 19 '18 at 22:30
I'm using us-east-1 region @JohnRotenstein
– alexVongola
Nov 20 '18 at 17:00