SUMMARY:
This is in line with RFC 3986:
http://tools.ietf.org/html/rfc3986#section-2.4
RELEVANT SECTION: Subscription and notification
COMMENT/REQUEST:
Basically, non-reserved characters in URLs should always be decoded by the
Hub for all input. That way, all subscriptions will refer to the same
canonical feed URL regardless of any weird encodings passed in by clients.
Subscribers should also do the right thing, but it's not as important.
Original issue reported on code.google.com by bslatkin on 4 Aug 2009 at 5:15
Original issue reported on code.google.com by
bslatkin
on 4 Aug 2009 at 5:15