Skip to content

fix(api): quote filename in Content-Disposition download header - #1265

Merged
harry0703 merged 1 commit into
harry0703:mainfrom
Mihir7027:fix/content-disposition-filename-quoting
Aug 26, 2026
Merged

fix(api): quote filename in Content-Disposition download header#1265
harry0703 merged 1 commit into
harry0703:mainfrom
Mihir7027:fix/content-disposition-filename-quoting

Conversation

@Mihir7027

Copy link
Copy Markdown
Contributor

Summary

  • The Content-Disposition header in the video download endpoint was building an unquoted filename token.
  • Per RFC 6266, the filename parameter must be a quoted-string. An unquoted filename containing spaces or special characters produces a malformed header, which causes browsers to truncate or reject the suggested filename.

Change

# Before
f"attachment; filename={filename}{extension}"

# After
f'attachment; filename="{filename}{extension}"'

Test plan

- [ ] Download a video whose filename contains a spaceconfirm the browser saves it with the full, correct filename.
- [ ] Download a video with a normal alphanumeric filenameconfirm no regression.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7d47ab6056

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread app/controllers/v1/video.py Outdated
…ame quoting

The previous manual header built an unquoted filename token, and a
simple-quoted fix would still produce malformed output for filenames
containing double-quotes or backslashes (e.g. name="draft".mp4 →
filename="name="draft".mp4").

Starlette's FileResponse(filename=...) already handles all
quoted-string escaping per RFC 6266, so drop the hand-rolled header
entirely and let the framework build it correctly. Also simplify
file_path.stem + extension back to file_path.name since stem+suffix
was a round-trip to the same value.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@Mihir7027
Mihir7027 force-pushed the fix/content-disposition-filename-quoting branch from 7d47ab6 to 85d321d Compare August 25, 2026 18:11
@harry0703
harry0703 merged commit 0b699b3 into harry0703:main Aug 26, 2026
@harry0703

Copy link
Copy Markdown
Owner

Thanks for the fix! I’ve merged it and added regression coverage for ASCII, spaced, non-ASCII, and header-sensitive filenames on main.

@Mihir7027
Mihir7027 deleted the fix/content-disposition-filename-quoting branch August 26, 2026 05:56
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

Successfully merging this pull request may close these issues.

2 participants