We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
...so that clients can detect and avoid responses that are too big for them to handle.
example: http://www.evdemon.org/2015/learning-more-about-quill has a >1MB inline image in the post content (ie <img src="data:image/png;base64,...>), which is also hoisted into the og:image meta tag, so the total HTML size is >2MB. found in snarfed/bridgy#525.
<img src="data:image/png;base64,...>
og:image
(not high priority, obviously. thanks in advance. hope you all are good!)
The text was updated successfully, but these errors were encountered:
detect HTTP responses that are too big and don't fetch them. fixes #525
19e66ac
also includes a hopefully temporary URL blacklist, which is the actual fix for #525 until idno/known#1088 is implemented.
9feed59
No branches or pull requests
...so that clients can detect and avoid responses that are too big for them to handle.
example: http://www.evdemon.org/2015/learning-more-about-quill has a >1MB inline image in the post content (ie
<img src="data:image/png;base64,...>
), which is also hoisted into theog:image
meta tag, so the total HTML size is >2MB. found in snarfed/bridgy#525.(not high priority, obviously. thanks in advance. hope you all are good!)
The text was updated successfully, but these errors were encountered: