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

set Content-Length HTTP response header #1088

Closed
snarfed opened this issue Oct 24, 2015 · 0 comments
Closed

set Content-Length HTTP response header #1088

snarfed opened this issue Oct 24, 2015 · 0 comments

Comments

@snarfed
Copy link

snarfed commented Oct 24, 2015

...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.

(not high priority, obviously. thanks in advance. hope you all are good!)

snarfed added a commit to snarfed/bridgy that referenced this issue Oct 24, 2015
also includes a hopefully temporary URL blacklist, which is the actual fix for #525 until idno/known#1088 is implemented.
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