spf-discuss
[Top] [All Lists]

[spf-discuss] Re: Error in RFC4408: URL encoding

2006-10-02 05:55:30
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Frank Ellermann wrote:
Julian Mehnle wrote:
For Mail::SPF, I decided to do exactly that:
| use constant uri_unreserved_chars   => 'A-Za-z0-9\-._~';

[...]

you don't want the expansion of %{S} to include any ? & % # characters,
because that would clash with the other, literal ? & #s and any
literal % percent codes in the raw explanation string.

Makes sense.

Is "usually" good enough ?  What about wild and wonderful %[L}
constructs, did anybody try this ?  For query strings and even paths the
relevant server can catch odd interpretations of an upper case macro, but
for an "authority" (host) it's DNS, and DNS can't be smart, e.g. % isn't
the same as %25 in a label.

Correct.  But if you use upper-case macros in DNS labels (as opposed to in 
an explanation string), then you know what to expect.  I don't really see 
the point in using upper-case macros in DNS labels, though.

Apparently you propose "%-encode all characters not in 3986-<unreserved>
excl. backslash".  Is that exception for backslash necessary ?

No, the backslash is merely an escape character for Perl's regexp syntax.  
Without it, the following dash (-) could be interpreted as designating a 
character range (actually it doesn't, because it is immediately preceded 
by the end of another character range, but it still might confuse human 
readers).

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFIQrpwL7PKlBZWjsRAnGZAJ9KnccfokmkMYkMOWeHQdFcGCD/BgCfdsyX
vj6/d+s6DMl+M6lXgZ83i4w=
=ihXR
-----END PGP SIGNATURE-----

-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your 
subscription, 
please go to 
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com