Blog posts tagged "debugging"

WOE “GeoPlanet”: HTTP/1.1 406 Not Acceptable

November 19th, 2008

not simple polygons

Just putting a note here for the next time I’m working with the Yahoo! GeoPlanet APIs.

The conudrum: a HTTP GET on a given resource (http://where.yahooapis.com/v1/place/23511846?appid=$appid) works in the browser, and works with wget from the command line, but fails from within PHP with a 406 Not Acceptable.

The solution, append format=XML to the resource URL, because the service is blowing out its brains on a missing Accepts header.

And that folks is the magic of REST.

update 2008/12/04: quick scan of my referer logs suggests this is biting folks using lwp-simple and wget particularly hard.

Error Pages

August 22nd, 2004

I assume everyone does this but I’ll blog it anyway. One of the best ways to find out the technology powering a well designed site is to generate an error condition.

Most sites litter clues as to their implementation all over the place, must to consternation of the Cool URIs school of thought, but its an interesting paradox that the sites that are the most interesting, and best implemented are the ones that are most silent about their underlying technology. wget -S http://example.org can sometimes tell you a bit, but you really need an error message to uncover the deep dark secrets.

I was reminded of this quite by accident today, when I ran into an error on del.icio.us. The answer is Mason, which I must say raises my estimation of Mason considerably. Now if only it was open source.

update (2004/9/15): or flickr runs PHP and Smarty

Tagged: Uncategorized , , ,

PHP 4.3.2 and expat Problems!?!

June 22nd, 2003

I’ve had 2 strange bug reports for Magpie. The common element is PHP 4.3.2. Anyone known anything (anything!) at all about what might be causing these problems?

Bug 1. Mapgie returns only 1 item

I got a report from that when Magpie was parsing a certain feed it was only return the first item in the feed, though there were clearly 15 items in the feed, and it was well formed. I went around a few times with the bug report, couldn’t reproduce it, talked with the person who reported it, and was coming close to dispair when they reported that their web host had recently upgraded to PHP 4.3.2 which is when the problem began, and the problem went away when they upgraded expat from 1.95.2 to 1.95.6. Good news, problem solved (yeh!) but um, that was weird, there were no error messages, and I hate mysteries. (bug which fix themselves have a nasty habit of showing up again later)

Bug 2. Running out of memory

Then I got a report of someone using FoF and Magpie, and running out of memory after parsing a small number of feeds. FreeBSD, PHP 4.3.2, expat 1.95.6 (drat).

I haven’t gone digging deeply into this (how the hell do you profile PHP btw?) but I wondered if anyone else was seeing/hearing about similar issues with the PHP 4.3.2? Thanks.