content-disposition doesn't work for streamed response
Categories
(Core :: Networking: HTTP, defect, P3)
Tracking
()
People
(Reporter: askoro, Unassigned)
Details
(Whiteboard: [necko-triaged][necko-priority-new])
Reporter | ||
Updated•15 years ago
|
Reporter | ||
Comment 1•15 years ago
|
||
Comment 3•2 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Comment 4•1 years ago
|
||
The severity field is not set for this bug.
:Gijs, could you have a look please?
For more information, please visit BugBot documentation.
Comment 5•1 years ago
•
|
||
If anything this would need picking up in necko land as that's what handles parsing Content-Disposition
headers themselves - but I don't have a setup to run JSP or do "streaming" (unsure what that even means?) responses. So unsure this is even a problem still. Perhaps it would just need to be closed incomplete...
Comment 6•1 years ago
|
||
It seems like this is low impact but we'll have the team take a look (though we might just end up closing it - it might actually work now and I'm not sure it's worth the effort of setting up a JSP env).
Updated•1 years ago
|
Comment 7•1 year ago
|
||
Given that we've made a lot of changes to the handling of content-disposition over the last 14 years, and that it's a lot of effort to recreate the testcase, we'll just close it as incomplete.
If anyone finds we still have a problem here, or the actually manage to reproduce, please reopen.
Description
•