Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Fix parsing of Content-Disposition headers #4763

Merged
merged 4 commits into from
Feb 27, 2019

Conversation

richvdh
Copy link
Member

@richvdh richvdh commented Feb 27, 2019

TIL: filenames in content-dispostion headers can contain semicolons, and aren't %-encoded.

TIL: filenames in content-dispostion headers can contain semicolons, and aren't
%-encoded.
@richvdh richvdh requested a review from a team February 27, 2019 17:02
Copy link
Member

@erikjohnston erikjohnston left a comment

Choose a reason for hiding this comment

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

Seems legit other than it would be good to flesh out the docstrings a little?

"""Parse a Content-type like header.

Cargo-culted from `cgi`, but works on bytes rather than strings.
"""
Copy link
Member

Choose a reason for hiding this comment

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

What does this return?

@codecov
Copy link

codecov bot commented Feb 27, 2019

Codecov Report

Merging #4763 into develop will increase coverage by 0.03%.
The diff coverage is 96.55%.

@@             Coverage Diff             @@
##           develop    #4763      +/-   ##
===========================================
+ Coverage    75.08%   75.12%   +0.03%     
===========================================
  Files          340      340              
  Lines        34900    34918      +18     
  Branches      5719     5722       +3     
===========================================
+ Hits         26204    26231      +27     
+ Misses        7084     7074      -10     
- Partials      1612     1613       +1

@hawkowl hawkowl merged commit 68f47d6 into develop Feb 27, 2019
@hawkowl hawkowl deleted the rav/fix_content_disposition_parsing branch February 27, 2019 22:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants