General Community > Site Comments, Issues and Concerns

bogus Content-Disposition header field sent to Firefox

<< < (9/9)

Oldiesmann:

--- Quote from: reschke on February 02, 2012, 07:05:14 AM ---
--- Quote from: Illori on January 31, 2012, 04:34:55 PM ---
--- Quote from: SleePy on November 27, 2011, 11:14:26 PM ---Its not the fix we wanted to do (wanted to do urlencode but it causes other issues), but it does the job none the less.

--- End quote ---

also the developers have other things on their plate to work on.

--- End quote ---

Acknowledged. But please don't blame Mozilla when a future version of Firefox starts failing again.

--- End quote ---

What solution do you suggest then? The patch fixed the issue without breaking things more.

reschke:

--- Quote from: Oldiesmann on February 02, 2012, 11:40:43 AM ---
--- Quote from: reschke on February 02, 2012, 07:05:14 AM ---
--- Quote from: Illori on January 31, 2012, 04:34:55 PM ---
--- Quote from: SleePy on November 27, 2011, 11:14:26 PM ---Its not the fix we wanted to do (wanted to do urlencode but it causes other issues), but it does the job none the less.

--- End quote ---

also the developers have other things on their plate to work on.

--- End quote ---

Acknowledged. But please don't blame Mozilla when a future version of Firefox starts failing again.

--- End quote ---

What solution do you suggest then? The patch fixed the issue without breaking things more.

--- End quote ---

My understanding was that the fix hasn't been applied (the bug status still is "new").

Illori:
it has not been applied officially to 2.0 branch, the fix is already in place for future releases.

Navigation

[0] Message Index

[*] Previous page

Go to full version