On 12/22/10 2:08 AM, Andrea Messina wrote:
1)Apache mod_rewrite problem
When we receive a Salmon message with a verb "FOLLOW", it means that
someone starts following us.
Therefore, we must obtain the follower's public-key with the aim of
authenticate the received message, so we should start a discovery
process using the author-uri element inside the Salmon entry.
Usually, the uri is in the form of an http profile ID(e.g
Status.net--->http://NICK.status.net/user/1).
Besides this kind of URI
(http://ielts.status.net/main/xrd?uri=acct:n...@status.net), we should
also accept
(http://ielts.status.net/main/xrd?uri=http://NICK.status.net/user/1).
I have some problems dealing with the handling of the latter URI.
I use mod_rewrite and i set the following rule, on my personal SN:
RewriteRule ^webfinger/uri=(.*)$ webfinger/xrd.php?uri=$1 [L,QSA]
I notice that acct:.... uri type works well, whilst the other type
doesn't; The browser cuts off a slash("/") in the final uri.
I'm not sure I understand where this rewrite rule fits in... are you
trying to use this rewrite rule *on* a StatusNet server, and if so what
is it meant to accomplish? Or is that on some other software that you're
writing that's meant to be OStatus-compatible?
Are you meaning to have that uri parameter in the path instead of the
query string in the match portion of your rule? What's generating the
URLs that you're trying to match? If this is for webfinger lookups, how
does a browser end up rewriting the URL?
2)Regarding Salmon:
In general we should ONLY accept Salmon(verb = POST) from our
FOLLOWERS. Is it right??
That's up to your server policy; StatusNet accepts them so you can get
replies from people you don't personally subscribe to.
-- brion
_______________________________________________
StatusNet-dev mailing list
StatusNet-dev@lists.status.net
http://lists.status.net/mailman/listinfo/statusnet-dev
