You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@roller.apache.org by mn...@yahoo.com on 2006/07/02 02:12:59 UTC
custom ping targets
I have not been able to sucessfully ping My Yahoo. I have configured custom ping targets for both http://api.my.yahoo.com/RPC2 http://api.my.yahoo.com/rss/ping and neither work. Other sites like Icerocket.com cannot be pinged either, but I have been able to ping other sites like Technorati. I'm using the 2.1.1-incubating version of Roller. Has anyone else experienced similar problems?
- mike
Regarding Roller problems pinging IceRocket
Posted by Anil Gangolli <an...@busybuddha.org>.
I looked into the IceRocket ping issue.
The problem is that IceRocket, whether by ignorance or intention, has
implemented an incompatible variant of the common weblogUpdates.ping
mechanism. Their ping request accepts only one argument, the blog URL, and
their success-case response also is not properly structured (it is a simple
string rather than a struct with flerror and message members).
I'm pursuing two tacks in parallel: (1) I've contacted Blake Rhodes at
IceRocket, and requested that they consider putting up a compatible
weblogUpdates.ping endpoint. I'm not expecting rapid response here, but
this is the right thing to do in principle, since there is a defacto
standard spec that most of the rest of the world seems to adhere to. But
also (2) I've filed a Roller JIRA issue
http://opensource.atlassian.com/projects/roller/browse/ROL-1192, which I
hope to fix before the next Roller release to add configurable support for
non-conformant ping implementations like IceRocket.
Also before the next Roller release, I am hoping to add common ping target
definitions in default disabled state for most/all of the ping targets I
know about and can verify as working or get to work with this and similar
minor variations.
In the meantime, a workaround is to ping icerocket via ping services like
ping-o-matic or pingoat. (Expect additional delay and somewhat weaker
guarantees that your ping will be delivered.)
--a.
Regarding Roller problems pinging IceRocket
Posted by Anil Gangolli <an...@busybuddha.org>.
I looked into the IceRocket ping issue.
The problem is that IceRocket, whether by ignorance or intention, has
implemented an incompatible variant of the common weblogUpdates.ping
mechanism. Their ping request accepts only one argument, the blog URL, and
their success-case response also is not properly structured (it is a simple
string rather than a struct with flerror and message members).
I'm pursuing two tacks in parallel: (1) I've contacted Blake Rhodes at
IceRocket, and requested that they consider putting up a compatible
weblogUpdates.ping endpoint. I'm not expecting rapid response here, but
this is the right thing to do in principle, since there is a defacto
standard spec that most of the rest of the world seems to adhere to. But
also (2) I've filed a Roller JIRA issue
http://opensource.atlassian.com/projects/roller/browse/ROL-1192, which I
hope to fix before the next Roller release to add configurable support for
non-conformant ping implementations like IceRocket.
Also before the next Roller release, I am hoping to add common ping target
definitions in default disabled state for most/all of the ping targets I
know about and can verify as working or get to work with this and similar
minor variations.
In the meantime, a workaround is to ping icerocket via ping services like
ping-o-matic or pingoat. (Expect additional delay and somewhat weaker
guarantees that your ping will be delivered.)
--a.
Re: custom ping targets
Posted by Anil Gangolli <an...@busybuddha.org>.
Sorry for the very late response.
Try turning on debug logging for the following categories, by putting these
lines in your log4j.properties in WEB-INF/classes under the roller webapp
and restarting:
log4j.category.org.apache.roller.presentation.pings.WeblogUpdatePinger=DEBUG
log4j.category.org.apache.roller.presentation.weblog.actions.PingSetupAction=DEBUG
Then try a sending test ping ("Send Ping Now") on this target from the Pings
tab on your blog.
People all over the net have been complaining that the yahoo ping receiver
has started returning 403 Forbidden on this URL. I'm not sure if this is
intentional on Yahoo's part or something else. It doesn't seem to be solely
a Roller issue though. I suspect you're getting this as well.
The icerocket issue seems to be different; it looks like it may be a bug in
the xmlrpc code we're using or in the Roller ping code that calls it. I've
started to investigate. I will let you know what I find.
--a.
----- Original Message -----
From: <mn...@yahoo.com>
To: <ro...@incubator.apache.org>
Sent: Saturday, July 01, 2006 5:12 PM
Subject: custom ping targets
>I have not been able to sucessfully ping My Yahoo. I have configured
>custom ping targets for both http://api.my.yahoo.com/RPC2
>http://api.my.yahoo.com/rss/ping and neither work. Other sites like
>Icerocket.com cannot be pinged either, but I have been able to ping other
>sites like Technorati. I'm using the 2.1.1-incubating version of Roller.
>Has anyone else experienced similar problems?
>
> - mike
>
>