Skip to content

Fixes #1828#1887

Merged
alexeyzimarev merged 1 commit intodevfrom
non-ascii-filename
Jul 7, 2022
Merged

Fixes #1828#1887
alexeyzimarev merged 1 commit intodevfrom
non-ascii-filename

Conversation

@alexeyzimarev
Copy link
Copy Markdown
Member

Description

Ability to tune the Content-Disposition header behaviour for files. All AddFile overloads now have the optional options parameter. It should be an instance of FileParameterOptions, which has two properties:

  • DisableFilenameEncoding - completely disables the default header behaviour and sends the filename raw. In most cases, it won't work. Default is false.
  • DisableFileNameStar - disables adding the filename* part of the header. Default is true as it's how the current version works. It should actually solve the problem described in the issue when set to true.

#1828

Purpose

This pull request is a:

  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

@alexeyzimarev alexeyzimarev merged commit c969747 into dev Jul 7, 2022
@repo-ranger repo-ranger bot deleted the non-ascii-filename branch July 7, 2022 14:07
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.

1 participant