| Anonymous | Login | Signup for a new account | 12-15-2025 02:18 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0001325 | [Resin] | major | always | 09-01-06 06:38 | 06-21-07 17:19 | ||||
| Reporter | slonopotamus | View Status | public | ||||||
| Assigned To | ferg | ||||||||
| Priority | normal | Resolution | fixed | Platform | any | ||||
| Status | closed | OS | any | ||||||
| Projection | none | OS Version | any | ||||||
| ETA | none | Fixed in Version | 3.1.2 | Product Version | 3.0.21 | ||||
| Product Build | |||||||||
| Summary | 0001325: Wrong error-page handling | ||||||||
| Description |
Java Servlet Specification v. 2.4: SRV.9.9.3 Error Filters The error page mechanism operates on the original unwrapped/unfiltered request and response objects created by the container. JBoss and Sun Java Application Server do this. But Resin (and, actually, Jetty too) does error handling in filtered request. |
||||||||
| Steps To Reproduce |
Deploy http://slonopotamus.org/error-page-bug.war [^] and open any nonexistent page. On System.err you'll get: before chain before chain in error page after chain after chain Expected output: before chain after chain before chain in error page after chain |
||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
Notes |
|
|
(0001494) slonopotamus 09-01-06 06:40 |
Please, view this issue in Advanced mode, because there are steps to reproduce. |
|
(0001495) slonopotamus 09-01-06 08:03 |
Same issue in Jetty: http://jira.codehaus.org/browse/JETTY-105 [^] |
|
(0001761) slonopotamus 02-12-07 12:45 |
Hello? |
|
(0002077) ferg 06-21-07 17:19 |
server/10s{o,p} |
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
36 total queries executed. 29 unique queries executed. |