|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 3983 | minor | always | 04-06-10 09:02 | 01-19-11 14:47 | |
|
|
|||||
| Reporter: | alex | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.1.8 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.15 | ||
|
|
|||||
| Summary: | 0003983: gzip filter ?>jsp->jsp->include->errorpage results in a broken content | ||||
| Description: |
broken stream is sent to the client upon an error if page throws an exception after the response has already been flushed. |
||||
| Steps To Reproduce: | |||||
| Additional Information: |
We may have found a problem with the Gzip filter in Resin Pro 3.1.8. In the attached example we have a page, gziptest.jsp, which, way down on the page after a lot of content, includes another jsp page, gzipinclude.jsp (pageContext.include). The main jsp page has an errorPage directive, the included jsp does not. If the included file throws an exception, the gzip filter seems to not work correctly. The user gets an "Content encoding error" (Firefox), or in IE: "Internet Explorer cannot display the webpage". The problem only occurs if the main page has an errorPage directive, and the included page doesn't. If the included page is included early in the main page, the problem don't occur, so it looks like this has something to do with content already been sent to the client when the exception occurs. |
||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||