http://bugzilla.novell.com/show_bug.cgi?id=512549
User jsmeix@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=512549#c3
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEEDINFO
Info Provider| |mzugec@novell.com
--- Comment #3 from Johannes Meixner 2009-06-24 02:04:24 MDT ---
What do you mean with "problem ... different syntax"?
I am mainly interested in percent-encoding of the value sub-strings
of an URI (e.g. values for username and password).
I am not interested in percent-encoding of a whole URI.
http://www.rfc-editor.org/rfc/rfc3986.txt
reads:
-------------------------------------------------------------------------
A URI is composed from a limited set of characters consisting of
digits, letters, and a few graphic symbols. A reserved subset of
those characters may be used to delimit syntax components within a
URI while the remaining characters, including both the unreserved set
and those reserved characters not acting as delimiters, define each
component's identifying data.
2.1. Percent-Encoding
A percent-encoding mechanism is used to represent a data octet in a
component when that octet's corresponding character is outside the
allowed set or is being used as a delimiter of, or within, the
component.
-------------------------------------------------------------------------
As far as I understand RFC 3986, the Example 141 in
http://forgeftp.novell.com//yast/doc/SL11.1/modules/URL.html#EscapeString
is plain wrong because it does percent-encoding for characters
which are actually meant to be delimiters in the URI
so that the resulting string in Example 141 is no longer a valid URI.
Furthermore regarding
http://forgeftp.novell.com//yast/doc/SL11.1/modules/URL.html
"RFC 2396 (updated by RFC 2732)"
is outdated, search for "3986" in
http://www.rfc-editor.org/cgi-bin/rfcsearch.pl
and you get
---------------------------------------------------------------------
RFC3986 ... Obsoletes RFC2732, RFC2396, RFC1808,
---------------------------------------------------------------------
It seems the YaST URL module needs a revision?
Perhaps it is better when I implement my own percent-encoding
function in yast2-printer in good compliance to RFC3986
than to incur bugs by using an partially outdated/obsoleted
implementation?
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
