| Type | Issue | Status | reviewed | Date | 8-Nov-2009 10:48 |
|---|---|---|---|---|---|
| Version | alpha 94 | Category | Datatype | Submitted by | meijeru |
| Platform | All | Severity | minor | Priority | normal |
| Summary | URL scheme characters admitted by DECODE-URL more restrictive than those admitted by TRANSCODE |
|---|---|
| Description |
DECODE-URL parses the scheme part of an URL (before :) with the following charset: A - Z a - z 0 - 9 + - . (this is in accordance with RFC 1738). Then it does TO-LIT-WORD, which eliminates the case of an initial digit or + -, which seems to be allowed by RFC 1738. TRANSCODE (i.e. the lexical scan) admits the following characters before the characteristic : of a URL! literal: in initial position A - Z a-z ! & = ? * . ^ _ ` | ~ (note the absence of digits and + -). In subsequent positions: anything from ! to ~ except [ ] { } ( ) " / : Thus TRANSCODE is much more permissive than either RFC 1738 or DECODE-URL. The restrictions mentioned would merit documenting, I think. |
| Example code |
| Assigned to | n/a | Fixed in | - | Last Update | 24-Nov-2009 04:34 |
|---|
| Date | User | Field | Action | Change |
|---|---|---|---|---|
| 24-Nov-2009 04:34 | carl | Status | Modified | submitted => reviewed |
| 8-Nov-2009 13:18 | meijeru | Summary | Modified | URL scheme characters admitted by DECODE-URL incompatible with those admitted by TRANSCODE => URL scheme characters admitted by DECODE-URL more restrictive than those admitted by TRANSCODE |
| 8-Nov-2009 13:18 | meijeru | Description | Modified | - |
| 8-Nov-2009 12:06 | meijeru | Description | Modified | - |
| 8-Nov-2009 10:48 | meijeru | Ticket | Added | - |