hi,
Saturday, May 6, 2006, 9:20:34 PM, you wrote:
>>> The important question here is: are there rules what character an URL
>>> can contain and what not?
vv>> yes, there is rfc3986.
vv>> and it doesn't seem to be obsoleted or updated by any other rfc,
vv>> judging by http://www.rfc-editor.org/rfc-index2.html
> I found this in RFC3986:
> 2.4. When to Encode or Decode
[^Y]
> I understand this means that not only the tilde but also umlauts are
> allowed. Or am I reading this wrong?
depending on how do you understand it.
basically, this means that WHEN/IF the user got a URI that *IS* (and i stress this!) %-encoded, the user may be *PRESENTED* WITH IT in a decoded form. this is exactly what browsers do - htey present you with umlauts in the address bar.
what you seem to definitely miss, is the difference between the PRESENTATION (applied to browsers' address bar) and RECOGNITION of an uri in an arbitrary text (which is the case of our message viewers)...
--
regards,
vitalie mailto:[EMAIL PROTECTED]
________________________________________________________ Current beta is 3.80.03 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
