More Code Debugging
Since some of the pings went through, I'm leaving the links to the places I tried to ping below. I have successfully pinged CNET News.com and Josiah's blog (in two different entries by accident — I am sorry Josiah!). I have not successfully pinged Christopher's blog, however. I thought I had, but due to a complex set of events that I shall explain sometime soon, I did not do so last night. Further attempts today seem to reveal something odd — WIT's copy of WordPress refuses to acknowledge that my posts link to a given entry, therefore making it impossible to do a proper pingback.
All else being equal, you'd think sending pingbacks to two WordPress blogs would return the same results, but for some reason it doesn't. I suspect that, for whatever reason, Christopher's server cannot connect to mine. Since inability to connect (or the returning of a 500 Internal Server Error “thanks” to mod_security) seems to be the only thing that invokes the error at hand in the case of my page, that seems to be the only thing I can figure. It could be more layers of security getting in the way perhaps, I'll have to try turning of mod_security again. To provide another view, I copied out WordPress' pingback code into a standalone PHP script and placed that on ibiblio.org — it, like Josiah's copy of WordPress, returns a successful code. We'll see what I find in the next few days.
Anyway, interesting stuff, I suppose. It might seem more so, tomorrow.
http://whatintarnation.net/blog/archives/2005/01/06/blast-from-the-past-ii-my-first-field-trip/ For debug purposes, please ignore.
Join the Conversation
Re: More Code Debugging
So do you have any suggestions for what I can do?
Re: More Code Debugging
Yes, WIT has had troubles with all sorts of pings, so it might be a problem with (of? ) cranium leakage?
Re: More Code Debugging
Ping at will Tim. I don’t mind. Ultimately it is a form of historical data.
Re: More Code Debugging
Re: More Code Debugging
I’ll e-mail you.
Re: More Code Debugging
Got your email and responded.