You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are proposing a change in the way we handle the 'Content-Disposition' header in file responses. Currently, the header includes both 'filename' and 'filename*' parameters for all file names. This change will make it so that the 'filename*' parameter is only used when the file name contains non-ASCII characters. This approach aligns better with the RFC 6266 standard and improves handling of file names with special characters.
The text was updated successfully, but these errors were encountered:
We are proposing a change in the way we handle the 'Content-Disposition' header in file responses. Currently, the header includes both 'filename' and 'filename*' parameters for all file names. This change will make it so that the 'filename*' parameter is only used when the file name contains non-ASCII characters. This approach aligns better with the RFC 6266 standard and improves handling of file names with special characters.
The text was updated successfully, but these errors were encountered: