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.

Sign up for GitHub

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

Jump to bottom

Telegram content proxy: inline images and other supported data types #165

Closed
ForNeVeR opened this issue Aug 28, 2022 · 0 comments · Fixed by #166
Closed

Telegram content proxy: inline images and other supported data types #165

ForNeVeR opened this issue Aug 28, 2022 · 0 comments · Fixed by #166
Assignees
@ForNeVeR
Labels
kind:feature

Comments

@ForNeVeR
Copy link
Member

Right now, everything gets downloaded as attachment, but we may do better. Consider either removing the Content-Disposition header, or making it inline.

Seemingly this could be done by removing the file name from the FileStream, but need experimentation. Maybe only remove that header if the MIME type is not application/octet-stream.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ForNeVeR ForNeVeR

Labels
kind:feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Content proxy improvements codingteam/emulsion
1 participant
@ForNeVeR