[MAGNOLIA-7121] Invalid Characters in URL cause Error 500 Created: 24/Aug/17 Updated: 16/Jun/21 Resolved: 16/Jun/21 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.9 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Julian Nodarse | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| 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)
|
||||
| Date of First Response: | |||||
| Description |
|
If a page is requested with invalid characters within a URL, the user will receive Error 500. An example would be something like : http://localhost:8080/magnoliaPublic/trav[el.html . Where the "[" is the invalid character. The error seems to be coming from the ContentType filter. Ideally, some sort of error handling would be placed within here so that Error 500 would not show. Just as examples, perhaps an Error 400 or 404 would be shown instead. |
| Comments |
| Comment by Jan Haderka [ 16/Jun/21 ] |
|
As of 6.2.9 the described scenario results in "400 - Bad Request" error instead. |