[MAGNOLIA-2005] response status code is always reset to http 200 by rendering filter Created: 15/Jan/08 Updated: 23/Jan/13 Resolved: 15/Jan/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 3.5.3 |
| Fix Version/s: | 3.5.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | Fabrizio Giustina | Assignee: | Fabrizio Giustina |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
When using magnolia in order to render also error pages (typically for 404/not found pages) any status code gets reset in rendering filter, leading to an http 200 also in case of errors. |
| Comments |
| Comment by Fabrizio Giustina [ 15/Jan/08 ] |
|
fix committed for 3.5.4 |
| Comment by Magnolia International [ 15/Jan/08 ] |
|
so the container is supposed to set a 200 by default ? |
| Comment by Fabrizio Giustina [ 15/Jan/08 ] |
|
> so the container is supposed to set a 200 by default ? yes, you can easily check the status code in the page info dialog in firefox... any request where the status code is not set explicitly gets a 200 by default |