Opened 15 years ago
Closed 14 years ago
#146 closed defect (fixed)
Illegal character handling not robust
| Reported by: | heikki | Owned by: | pieterv |
|---|---|---|---|
| Priority: | minor | Milestone: | v2.5.1 |
| Component: | General | Version: | v2.4.1 |
| Keywords: | xslt character illegal | Cc: |
Description
If your DB contains a character that is not allowed by the spec (I believe it's the range decimal 127-159 inclusive), GeoNetwork's XSLT transformation will choke on it, go to the error page and put out a message such as:
SERE0014: Illegal HTML character: decimal 157
It would be better to handle this more gracefully. Maybe we can either scan all chars coming out of the DB for illegal characters, and take them out before further processing; or gain some performance by assuming it almost never happens, catch this exception and then strip illegal characters from it.
Attachments (1)
Change History (6)
comment:1 by , 14 years ago
| Owner: | changed from to |
|---|
comment:2 by , 14 years ago
| Status: | new → assigned |
|---|
comment:3 by , 14 years ago
| Milestone: | v2.5.0 → v2.5.1 |
|---|
by , 14 years ago
comment:4 by , 14 years ago
attached a patch, implementing this approach: "scan all chars coming out of the DB for illegal characters, and take them out before further processing"
patch