Skip to content

Syntactically invalid blobs become inaccessible #106

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

Closed
Squornshellous-Beta opened this issue Feb 17, 2025 · 0 comments
Closed

Syntactically invalid blobs become inaccessible #106

Squornshellous-Beta opened this issue Feb 17, 2025 · 0 comments

Comments

@Squornshellous-Beta
Copy link

Squornshellous-Beta commented Feb 17, 2025

It is possible to submit a PUT request containing an invalid object. If this is done, the blob seemingly becomes inaccessible; GET requests appear to return normally but with undefined or unusable contents, and attempting to view the blob's webpage returns a 524 timeout. Another PUT request can still edit it, but this makes debugging more difficult, as one cannot see the data which caused the error nor manually correct it. An example can be seen here, which contains an unterminated string.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant