Julian Mehnle wrote:
For Mail::SPF, I decided to do exactly that:
| use constant uri_unreserved_chars => 'A-Za-z0-9\-._~';
[...]
within the SPF spec, URL-escaping AKA percent-encoding is
only applied for upper-case macro expansion, which itself is
usually only used in "exp=" explanation string expansion
exp TXT "http://www.%{d2}/why.html?s=%{S}&i=%{I}";
[...]
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.
You are always free to use literal # [ ] (and other
non-"unreserved" characters) _literally_ in your explanation
string:
TXT http://www.%{d2}/why.html?s=%{S}&i=[%{I}]#fragment";
Add &l=%{L} for more fun. Apparently you propose "%-encode all
characters not in 3986-<unreserved> excl. backslash". Is that
exception for backslash necessary ?
Frank (in need of more coffee)
--
Honk for 4234 to STD
-------
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