Skip to content
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

Invalid character reference in XML response #8894

Closed
cyberduck opened this issue Jun 23, 2015 · 2 comments
Closed

Invalid character reference in XML response #8894

cyberduck opened this issue Jun 23, 2015 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jun 23, 2015

e79d7e4 created the issue

Hello

I am trying to connect to my S3 account. I can get to the root directory, but when I try to open a sub-directory I get the following error:

Listing directory leanculturegroup failed 
Character reference "&#.

Log File:

GET /?max-keys=1000&prefix&delimiter=%2F HTTP/1.1
Date: Tue, 23 Jun 2015 17:33:09 GMT
Authorization: AWS AKIAJC334APY57DH5N4A:H5M79kfoq8PLxplwFoqRJ6hM4wc=
Host: leanculturegroup.s3.amazonaws.com:443
Connection: Keep-Alive
User-Agent: Cyberduck/4.7.1.17795 (Mac OS X/10.10.3) (x86_64)
HTTP/1.1 200 OK
x-amz-id-2: SwLnyLynGoXxrYTwEfIZZcoqDXNZiDRWTMvGGK1cv6Kk0AeUhrWSndgcoyIklB8DCySvqEd0XmI=
x-amz-request-id: 2FA426E6ABF4BA1A
Date: Tue, 23 Jun 2015 17:33:12 GMT
Content-Type: application/xml
Transfer-Encoding: chunked
Server: AmazonS3

Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 24, 2015

@dkocher commented

There is an invalid character reference in the XML document returned by Amazon S3. If you can give us temporary read only access to the S3 bucket using an IAM user that would help trying to resolve this issue. Please email the credentials to [feedback@cyberduck.io].

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 25, 2015

@dkocher commented

Most possibly you have a key in your bucket that is named outside the UTF-8 character range and is therefore causing problem with an invalid XML response sent by S3. Please try to remove the file.

References

Loading

@cyberduck cyberduck closed this Jun 25, 2015
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant