Re: [webfinger] feedback for multiple "rel"

If we made it a requirement that "rel" values have no spaces (which I would
argue is a damn good thing for many reasons) then we would not have to
double-encode.

Paul

From: webfinger-bounces@ietf.org [mailto:webfinger-bounces@ietf.org] On
Behalf Of nov matake
Sent: Saturday, December 22, 2012 11:12 AM
To: Melvin Carvalho
Cc: webfinger@ietf.org
Subject: Re: [webfinger] feedback for multiple "rel"

BTW, why double encoding lead "problems with things like canonical urls and
search engines"?

Can you provide more details?

If 2 rel included, the response would be different than when only 1 rel
given.

So I feel those 2 are not the same, and can be indexed as 2 resources..

On 2012/12/23, at 0:44, Melvin Carvalho <melvincarvalho@gmail.com> wrote:

On 22 December 2012 05:48, nov matake <matake@gmail.com> wrote:

Hi,

I have a comment for they way to specify multiple "rel" values.

As a ruby library developer, my main target is rails developers.
Since rails can't handle multiple same query keys, developers will need to
hack query params parser in rails middleware layer.
I can easily imagine it'll be an annoying part to support webfinger in
rails.

Is the multiple "rel" case can be a space-delimitered (or some other
character) strings like multiple redirect_uri in OAuth2?
Or any reason for putting multiple same keys in query parameters?

each time you delimit a list, you have to be able to escape the delimiter,
which can be a pain and also leads to problems with things like canonical
urls and search engines

can you use mod_rewrite?

Cheers,

Nov Matake
_______________________________________________
webfinger mailing list
webfinger@ietf.org
https://www.ietf.org/mailman/listinfo/webfinger