Describe the bug
When piping a Workbook to HTTP response, Content-Disposition header is set to a string with trailing ";" e.g: attachment; filename="report.xlsx"; filename*=utf-8''report.xlsx;
According to RFC 2183, the syntax of Content-Disposition header does not imply having a ";" character at the end of the header value. This issue was discovered while passing header value to content-disposition's parse() function which was throwing an error about invalid parameter format
Describe the bug When piping a Workbook to HTTP response,
Content-Disposition
header is set to a string with trailing ";" e.g:attachment; filename="report.xlsx"; filename*=utf-8''report.xlsx;
According to RFC 2183, the syntax of Content-Disposition header does not imply having a ";" character at the end of the header value. This issue was discovered while passing header value to content-disposition's
parse()
function which was throwing an error about invalid parameter formatTo Reproduce
http://localhost:3000
with Postman or similar app.Content-Disposition
response header value.Expected behavior A
Content-Disposition
header should contain syntactically correct value w/o trailing ";"Environment